I suggest you look in your /var/log files to see if there's a clue there.
Doesn't seem to be much help ...
Sep 26 07:32:10 linux ipop3d[13043]: pop3 service init from 192.168.0.152
Sep 26 07:35:10 linux ipop3d[13043]: Autologout user=??? host=michael [192.168.0.152]
Sep 26 15:11:15 linux ipop3d[19795]: pop3 service init from 192.168.0.152
Sep 26 15:11:20 linux ipop3d[19795]: Command stream end of file, while reading authentication host=michael [192.168.0.152]
Sep 26 18:56:48 linux ipop3d[23312]: pop3 service init from 192.168.0.152
The messages vary only according to how the session was terminated, but it (on purpose, per the WU website) gives no clue about why authentication failed.
One thing that's fairly easy to do with courier-imap is to run the wrong authentication daemon (e.g. ldap instead of plain or mysql). If you're running most Linux systems with pam, you need to make sure that the appropriate pam.d/ file is correct (should look a lot like the normal pam.d/login file). In particular, if you're using pam_ldap and ldap authentication, make sure that this is specified.
I checked the pop and imap files under /etc/pam.d, and they appear identical to what I was using under RH8. Tho I'm not very deep into such.
Michael
_______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://mail.linux-sxs.org/mailman/listinfo/linux-users
