[Dovecot] dovecot 0.99 + apple mail.app
hello all,
first off, a success story. after much testing and preperation, we've switched from uw-imap to dovecot. i am not kidding when i say that we have experienced an order of magnitude decrease in server load (previously load peaks were 40-60, now they are 3-4). so, suffice to say that the mail admins here are very happy :)
one problem that has come up though is particular to apple's mail.app. when a client recieves a new message, they aren't notified that it's arrived, and often even when pressing "check for new mail" they don't see it come in. however, if they move from one mailbox to another, and then back, it shows up. it also shows up if thtey completely quit out of the program and start it back up.
i'm going to try and get a packet dump of this to see if i can find out what's happening in the conversation, but figured in the meantime i'd put my feelers out to see if anyone else is having this problem.
thanks, sean
On Mon, Mar 07, 2005 at 11:50:54AM -0500, sean finney wrote:
i'm going to try and get a packet dump of this to see if i can find out what's happening in the conversation, but figured in the meantime i'd put my feelers out to see if anyone else is having this problem.
I've been using dovecot with Apple Mail for a bit over a year now, and the only problem I see from time to time is that sent messages sometimes get truncated; that was fixed at some point in the 1.0 series. New mail notification works fine for me.
-- Nicholas Riley njriley@uiuc.edu | http://www.uiuc.edu/ph/www/njriley
On 7.3.2005, at 18:50, sean finney wrote:
one problem that has come up though is particular to apple's mail.app. when a client recieves a new message, they aren't notified that it's arrived, and often even when pressing "check for new mail" they don't see it come in. however, if they move from one mailbox to another, and then back, it shows up. it also shows up if thtey completely quit out of the program and start it back up.
i'm going to try and get a packet dump of this to see if i can find out what's happening in the conversation, but figured in the meantime i'd put my feelers out to see if anyone else is having this problem.
I've always had that problem, but I don't know what could be done about it. Mail.app simply doesn't read or write anything to the IMAP server unless it's specifically told to do something.
I heard from someone it was working with Courier, but with my Courier test server it didn't work. So, apparently it was working with UW-IMAP before? Perhaps I'll try it too to see if it does something differently..
On Mar 7, 2005, at 3:48 PM, Timo Sirainen wrote:
I've always had that problem, but I don't know what could be done about it. Mail.app simply doesn't read or write anything to the IMAP server unless it's specifically told to do something. I heard from someone it was working with Courier, but with my Courier test server it didn't work. So, apparently it was working with UW-IMAP before? Perhaps I'll try it too to see if it does something differently..
I just tested this again - I sent mail from Mail.app to two accounts, one of which is running Courier, and one of which is running dovecot 1.0-stable. For both accounts, Mail.app chimed to tell me I had new mail, 1 minute apart (delivery to the dovecot server takes longer because it runs through fetchmail/procmail/spamassassin). It was in the background with my "combined" inbox selected/displayed at the time.
The frequency with which it polls the server seems to be dictated by the Preferences > General > "Check for new mail:" interval, which I set to 1 minute for this test.
-- Nicholas Riley njriley@uiuc.edu | 4111 Siebel Center Department of Computer Science | 201 N. Goodwin Ave. and Medical Scholars Program | Urbana, IL 61801-2302 Univ. of Illinois at Urbana-Champaign | +1 217 244 2274
On 8.3.2005, at 00:06, Nicholas Riley wrote:
I just tested this again - I sent mail from Mail.app to two accounts, one of which is running Courier, and one of which is running dovecot 1.0-stable. For both accounts, Mail.app chimed to tell me I had new mail, 1 minute apart (delivery to the dovecot server takes longer because it runs through fetchmail/procmail/spamassassin). It was in the background with my "combined" inbox selected/displayed at the time.
The frequency with which it polls the server seems to be dictated by the Preferences > General > "Check for new mail:" interval, which I set to 1 minute for this test.
Oh, with INBOX it works. With other mailboxes it doesn't.
On Tue, Mar 08, 2005 at 12:24:23AM +0200, Timo Sirainen wrote:
Oh, with INBOX it works. With other mailboxes it doesn't.
Ah, OK, INBOX is all I care about. :)
BTW, the changes in -test63 seem to have fixed the crashing problems we were seeing, at least nothing so far. I got an message of this form I had not seen before:
dovecot: Mar 07 16:26:03 Error: IMAP(njr): Fixed index file /usr/home/njriley/mail/.imap/Deleted Messages/dovecot.index: recent_messages_count 2 -> 0
and I'm still getting these, but I guess they are harmless:
dovecot: Mar 07 16:27:58 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/subscriptions (7639 > 2)
-- Nicholas Riley njriley@uiuc.edu | http://www.uiuc.edu/ph/www/njriley
Nicholas Riley wrote:
On Tue, Mar 08, 2005 at 12:24:23AM +0200, Timo Sirainen wrote:
Oh, with INBOX it works. With other mailboxes it doesn't.
Ah, OK, INBOX is all I care about. :)
BTW, the changes in -test63 seem to have fixed the crashing problems we were seeing, at least nothing so far. I got an message of this form I had not seen before:
dovecot: Mar 07 16:26:03 Error: IMAP(njr): Fixed index file /usr/home/njriley/mail/.imap/Deleted Messages/dovecot.index: recent_messages_count 2 -> 0
and I'm still getting these, but I guess they are harmless:
dovecot: Mar 07 16:27:58 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/subscriptions (7639 > 2)
I've recently had a small issue w/ T-Bird on my wife's XP laptop since I've moved to Dovecot...the logs indicated she had a new msg., she thought she heard a "ding" indicating a new msg., but there was no indication of it in T-Bird, and clicking "Get Mail" didn't do anything. I hit the "offline" icon at the bottom corner, put it back online, and hit "Get Messages," and all was fine. So...problem w/ T-Bird or Dovecot, jury is out, but I have not seen any common occurrences of this issue, so nothing I'm all that worried about.
F. Even wrote:
I've recently had a small issue w/ T-Bird on my wife's XP laptop since I've moved to Dovecot...the logs indicated she had a new msg., she thought she heard a "ding" indicating a new msg., but there was no indication of it in T-Bird, and clicking "Get Mail" didn't do anything. I hit the "offline" icon at the bottom corner, put it back online, and hit "Get Messages," and all was fine. So...problem w/ T-Bird or Dovecot, jury is out, but I have not seen any common occurrences of this issue, so nothing I'm all that worried about.
There are two ways to fix this.
Thunderbird will let you set per-folder to check for new messages.
Right click the folder, select Properties, and tick "Check this folder for new messages".
-- Curtis Maloney cmaloney@cardgate.net
Timo Sirainen wrote:
On 8.3.2005, at 00:06, Nicholas Riley wrote:
I just tested this again - I sent mail from Mail.app to two accounts, one of which is running Courier, and one of which is running dovecot 1.0-stable. For both accounts, Mail.app chimed to tell me I had new mail, 1 minute apart (delivery to the dovecot server takes longer because it runs through fetchmail/procmail/spamassassin). It was in the background with my "combined" inbox selected/displayed at the time.
The frequency with which it polls the server seems to be dictated by the Preferences > General > "Check for new mail:" interval, which I set to 1 minute for this test.
Oh, with INBOX it works. With other mailboxes it doesn't.
This has been a known problem with Mail.app for a long time. (and a major reason why i switched to Thunderbird)
if you're doing serverside sorting (presumably using procmail or something equivalent) any new messages in any subfolders won't be recognized by Mail.app unless you click on that subfolder (or click out and back in)
that's a major pet peeve of mine with Mail.app
I've seen this with UW-imap, Courier and Dovecot.
Alan
Am 08.03.2005 um 8:06 Uhr +0900 schrieb alan premselaar:
Oh, with INBOX it works. With other mailboxes it doesn't.
This has been a known problem with Mail.app for a long time. (and a major reason why i switched to Thunderbird)
Eudora checks on a configurable selection of folders, too, since 6.1. A dream come true...
hauke-- /~\ The ASCII Ribbon Campaign Hauke Fath \ / No HTML/RTF in email Institut für Nachrichtentechnik X No Word docs in email TU Darmstadt / \ Respect for open standards Ruf +49-6151-16-3281
participants (7)
-
alan premselaar
-
Curtis Maloney
-
F. Even
-
Hauke Fath
-
Nicholas Riley
-
sean finney
-
Timo Sirainen