Ned, are you running courier's pop3d or qmail's?

I'm running courier's.

I'm not sure how the courier logger chooses to write to
/var/log/maillog tho... I suspect your pop3d is not set to write to
this log. ... And I don't know what would be causing the auth errors,
maybe a conflict between your pop3d and vpopmail.

-jesse


At 12:44 +0100 14/3/2003, Ned Baldessin wrote:
Vu "Re: [vchkpw] Password fail with specific MUA (Mail.app)", du
14/03/03 à 13:40 +1030 :
What method of connecting are your Mail.app users using? Just plain
old POP or what?

I was using plain POP with password auth. I just tried IMAP (with plain password too), and I *don't* get the errors :

Mar 14 12:32:54 ns3167 imapd: Connection, ip=[::ffff:81.56.85.236]
Mar 14 12:32:54 ns3167 imapd: LOGIN, [EMAIL PROTECTED],
ip=[::ffff:81.56.85.236]
Mar 14 12:32:57 ns3167 imapd: Connection, ip=[::ffff:81.56.85.236]
Mar 14 12:32:57 ns3167 imapd: LOGIN, [EMAIL PROTECTED],
ip=[::ffff:81.56.85.236]

I'm running the latest versions of OS X and Mail.app, they are Mac
OS X v10.2.4 and Mail 1.2.3 (v551)

Me too.


The only difference between our two logs I cab see is the fact that
when I fetch mail on a other MUA than Mail.app, I don't get a log
entry at all.
And also no trace of 'pop3d'.

Sorry if this sounds silly, I don't know much (yet) about vpopmail.

Thanks.
--
ned's key ID is 0x35359C2B





Reply via email to