Alexander Dalloz wrote:
>Am Fr, den 11.03.2005 schrieb Aleksandar Milivojevic um 21:36:
>
>
>
>>I believe I had it working with both shadow and pam on FC2 and FC3
>>boxes. When set to shadow, it simply reads /etc/shadow directly. When
>>set to pam, it will use whatever PAM mechanism is configured on the
>>system (for example, lookup users in NIS or NIS+ domains).
>>
>>
>
>Correct.
>
>
>
>>However, the system where I tested shadow as saslautd mechanism had only
>>crypted passwords in /etc/shadow. I don't know if shadow mechanism
>>works with MD5 passwords. If not, time to fill bug report ;-)
>>
>>
>
>No need to fill out a bug ticket. The sentence "/etc/sysconfig/saslauthd
>is distributed with MECH=shadow even though cyrus-imapd needs this value
>set to MECH=pam" by James B. Byrne is simply not true. I have more than
>1 system running with shadow as the saslauthd mechanism, and it works as
>it should.
>
>Alexander
>
>
>
Actually, you both may be right. Seems I had to jump through all those
hoops on one system. It may have something to do with how you do your
initial install of the system? After doing this once, suddenly it seemed
I never had to do it again. The only difference I can think of was I
learned what was and was not installed by default and learned to choose
these packages when doing a new system. Then again, I just might be all
wet behind the ears. It has been over a year now since I had this problem.
John Hinton
