Re: [vchkpw] Password fail with specific MUA (Mail.app)
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=[:::81.56.85.236] Mar 14 12:32:54 ns3167 imapd: LOGIN, [EMAIL PROTECTED], ip=[:::81.56.85.236] Mar 14 12:32:57 ns3167 imapd: Connection, ip=[:::81.56.85.236] Mar 14 12:32:57 ns3167 imapd: LOGIN, [EMAIL PROTECTED], ip=[:::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
Re: [vchkpw] Password fail with specific MUA (Mail.app)
Actually I think this error is related to the version of vpopmail you are using. Maybe try upgrading. On Sat, 15 Mar 2003 04:42, Ned Baldessin wrote: At 1:38 +1030 15/03/03, Jesse Reynolds wrote: 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. I'm pretty shure qmail's pop3d is used for POP, and courier is only used for IMAP. Vpopmail is set to log only errors to /var/log/maillog. Well, I'm lost. I guess the next step is to sniff the data that Mail.app is sending and compare it to, say, what Eudora is sending. But that would be a hassle.
Re: [vchkpw] Password fail with specific MUA (Mail.app)
Hi Ned I run Mail.app for some of my email, and have not seen these errors you're talking about. I'm connecting via Courier-IMAP's SSL service, and I see the following at login: Mar 14 13:30:18 shiraz imapd-ssl: Connection, ip=[:::150.101.22.162] Mar 14 13:30:18 shiraz imapd-ssl: LOGIN, [EMAIL PROTECTED], ip=[:::150.101.22.162] so obviously no errors there. What method of connecting are your Mail.app users using? Just plain old POP or what? Testing a plain POP login is also fine for me: Mar 14 13:34:39 shiraz pop3d: Connection, ip=[:::150.101.22.162] Mar 14 13:34:39 shiraz pop3d: LOGIN, [EMAIL PROTECTED], ip=[:::150.101.22.162] Mar 14 13:34:39 shiraz pop3d: LOGOUT, [EMAIL PROTECTED], ip=[:::150.101.22.162], top=0, retr=0 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) Cheers Jesse At 2:22 +0100 14/3/2003, Ned Baldessin wrote: Hello, Each time a user checks his account using the MacOSX Mail.app MUA, I get an error in my maillog. Mar 14 01:27:01 ns3167 vpopmail[9164]: vchkpw: password fail [EMAIL PROTECTED]:81.56.96.75 Mar 14 01:27:01 ns3167 vpopmail[9165]: vchkpw: password fail [EMAIL PROTECTED]:81.56.96.75 Mar 14 01:27:43 ns3167 vpopmail[9174]: vchkpw: password fail [EMAIL PROTECTED]:81.56.96.75 Mar 14 01:27:43 ns3167 vpopmail[9176]: vchkpw: password fail [EMAIL PROTECTED]:81.56.96.75 Observations : - The users can perfectly well receive their email, the MUA doesn't complain (no errors on the user-side). - This only happens with the Mail.app MUA. I have cross checked this with other MUAs on other domains (same server). - I'm running vpopmail 5.2.1 on a RH 7.2 box. I have no idea if the problem is with vpopmail or with Apple's Mail.app. Any suggestions are welcome. Thanks. -- ned's key ID is 0x35359C2B
