Hi,
I solved the OSX Authentication issue; I'm now reliably able to get authenticated using the Password Server with PAM with:
# login: auth account password session auth required pam_nologin.so auth sufficient pam_securityserver.so auth sufficient pam_unix.so auth required pam_deny.so account required pam_permit.so password required pam_deny.so session required pam_permit.so
As the /etc/pam.d/imap
Anyway -- new problem. With Apple's Mail.app and how it wants to download messages into it's cache, I've found that there's a problematic interaction between Dovecot and Mail.app -- but pinning down exactly what and where is proving to be a hassle.
I was running Courier-Imap with Mail.app, and that worked without incident (however, the courier-imap server was on Linux, not OSX Server, that will not work (yet) with osx-server).
If I use Entourage and Dovecot, it works fine.
The primary symptom is that as it downloads messages Mail.app just hangs; no response, the session just freezes. Usually it's when the status bar is saying something akin to "Caching 9 of 506" at which point it stops. The number varies, but it's always in the first couple of dozen. Messages are small, so it's not that it's hanging on a large mail download. I eventually have to forcibly kill Mail.app.
The log says nothing of use:
dovecot: Mar 07 17:31:23 Info: Dovecot starting up imap-login: Mar 07 16:32:50 Info: Login: scott [194.109.29.21] imap-login: Mar 07 16:33:46 Info: Login: scott [194.109.29.21] imap-login: Mar 07 16:35:38 Info: Login: scott [194.109.29.21]
But perhaps there's a more verbose option somewhere.
Thoughts?
Scott
On Fri, Mar 07, 2003 at 05:39:10PM +0100, Scott A.McIntyre wrote:
The primary symptom is that as it downloads messages Mail.app just hangs; no response, the session just freezes. Usually it's when the status bar is saying something akin to "Caching 9 of 506" at which point it stops. The number varies, but it's always in the first couple of dozen. Messages are small, so it's not that it's hanging on a large mail download. I eventually have to forcibly kill Mail.app.
My best guess is that it uses FETCH ENVELOPE, which is somewhat broken in 0.99.8 if some headers (subject, in-reply-to mostly) contain '"' characters. BODY and BODYSTRUCTURE fetches can also break but they're less likely to contain '"' chars.
Try if the included patch fixes. Dovecot may have cached those replies already, so delete all .imap.index* files.
Hi,
Try if the included patch fixes. Dovecot may have cached those replies already, so delete all .imap.index* files. <quote.diff>
Turns out that patch is already in CVS -- I took a stab at trying the CVS version earlier (around 1500 today) just in case whatever it was was fixed from 0.99.8 to CVS. Same result. --version still says 0.99.8, but it's definitely the newer one.
I'd have thought it would break with Entourage as well if it were this, though...
Scott
On Fri, 2003-03-07 at 18:57, Scott A. McIntyre wrote:
Try if the included patch fixes. Dovecot may have cached those replies already, so delete all .imap.index* files. <quote.diff>
Turns out that patch is already in CVS -- I took a stab at trying the CVS version earlier (around 1500 today) just in case whatever it was was fixed from 0.99.8 to CVS. Same result. --version still says 0.99.8, but it's definitely the newer one.
And you tried to delete .imap.index* files too? :)
Well, I'd like to know what exactly it's talking to IMAP server. Either use some network sniffer, or configure Dovecot --with-rawlog, and create ~/rawlog directory where they're saved.
I think some people have already tried Mail.app with 0.99.7 and it worked..
I've been using dovecot (a co & build from dec. 28th) without this problem with Mail.app just fine even with it's cacheing option turned on (i have it off now). Granted, the server is on a netbsd/i386 machine, I doubt that'd make a difference.
Scott A. McIntyre wrote:
Hi,
Try if the included patch fixes. Dovecot may have cached those replies already, so delete all .imap.index* files. <quote.diff>
Turns out that patch is already in CVS -- I took a stab at trying the CVS version earlier (around 1500 today) just in case whatever it was was fixed from 0.99.8 to CVS. Same result. --version still says 0.99.8, but it's definitely the newer one.
I'd have thought it would break with Entourage as well if it were this, though...
Scott
-- Jesse Peterson / jesse@pixeltechs.com
participants (4)
-
Jesse Peterson
-
Scott A. McIntyre
-
Scott A.McIntyre
-
Timo Sirainen