[Dovecot] Outlook express confusion
Hi,
This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message. Since it is affecting my boss he has told me to go back to test60 or lower, and won't let me find the problem.
Regards Andrew
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Cosmic ray particles crashed through the hard disk platter
On Fri, 2005-04-08 at 12:23 +0100, Andrew Hutchings wrote:
This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message.
Hmm. And nothing in log file? Were the messages expunged recently (less than an hour ago) or did some older messages also appear? Only OE-related thing that I can think of is this change:
2005-03-14 21:17 Timo Sirainen tss@iki.fi
* dovecot-example.conf, src/imap/cmd-fetch.c, src/imap/common.h,
src/imap/imap-sync.c, src/imap/main.c,
src/lib-storage/mail-storage.h,
src/lib-storage/index/index-sync.c: Renamed oe6-fetch-no-newmail
workaround to delay-newmail and changed it to work more like the
name says: only newmail notifications are skipped and not only
for FETCH command.But that shouldn't be making expunged mails visible.. Nothing should actually. Unless new messages are getting UIDs from old mails (there is/was a bug like that with mbox, but not maildir AFAIK).
If anyone can find a way to reproduce this I'd like to know.
Hi Timo, Nada in the log file. Messages were expunged within a minute of getting deleted. My boss says after expunging he mainly got blank messages where the deleted ones were, no subject, from, or anything and message unreadable when read (I don't have OE here so can't verify), but someone else in the office had the same problem and said that a customer did as well. I will setup a test bed over the weekend to try and duplicate/trace it. I was thinking it might be related to that work around but I can't give any more info just as yet. Forgot to mention it is using Maildir, LVS -> 2 dovecot servers -> 1 nfs server, indexes stored locally, IMAP on LVS is set to persistent connections. Test 60 works fine though with this.
BTW. Just applied your new message-address.c patch to test 60 (as well as the one from Mar 24) and got 'Full Name@UNKNOWN DOMAIN' in OE when address is '"Full Name" user@domain.com'. I probably missed another patch somewhere in my haste to get this going though :)
Regards Andrew
On Fri, 2005-04-08 at 16:27 +0300, Timo Sirainen wrote:
On Fri, 2005-04-08 at 12:23 +0100, Andrew Hutchings wrote:
This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message.
Hmm. And nothing in log file? Were the messages expunged recently (less than an hour ago) or did some older messages also appear? Only OE-related thing that I can think of is this change:
2005-03-14 21:17 Timo Sirainen tss@iki.fi
- dovecot-example.conf, src/imap/cmd-fetch.c, src/imap/common.h, src/imap/imap-sync.c, src/imap/main.c, src/lib-storage/mail-storage.h, src/lib-storage/index/index-sync.c: Renamed oe6-fetch-no-newmail workaround to delay-newmail and changed it to work more like the name says: only newmail notifications are skipped and not only for FETCH command.
But that shouldn't be making expunged mails visible.. Nothing should actually. Unless new messages are getting UIDs from old mails (there is/was a bug like that with mbox, but not maildir AFAIK).
If anyone can find a way to reproduce this I'd like to know.
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: the real ttys became pseudo ttys and vice-versa.
On Fri, 2005-04-08 at 14:49 +0100, Andrew Hutchings wrote:
Just applied your new message-address.c patch to test 60 (as well as the one from Mar 24) and got 'Full Name@UNKNOWN DOMAIN' in OE when address is '"Full Name" user@domain.com'. I probably missed another patch somewhere in my haste to get this going though :)
Hmm. Are some people actually using such addresses? It's not valid if there aren't <> between the address. UW-IMAP gives this for such address:
(NIL NIL "Timo Sirainen" ".MISSING-HOST-NAME.")(NIL NIL "UNEXPECTED_DATA_AFTER_ADDRESS" ".SYNTAX-ERROR.")
That new patch was fixing a case where "User name"@domain address wasn't working.
Hi Timo,
Apologies I meant '"Full Name" user@domain.com' shows as 'Full Name@MISSING_DOMAIN'
Regards Andrew
On Fri, 2005-04-08 at 17:00 +0300, Timo Sirainen wrote:
On Fri, 2005-04-08 at 14:49 +0100, Andrew Hutchings wrote:
Just applied your new message-address.c patch to test 60 (as well as the one from Mar 24) and got 'Full Name@UNKNOWN DOMAIN' in OE when address is '"Full Name" user@domain.com'. I probably missed another patch somewhere in my haste to get this going though :)
Hmm. Are some people actually using such addresses? It's not valid if there aren't <> between the address. UW-IMAP gives this for such address:
(NIL NIL "Timo Sirainen" ".MISSING-HOST-NAME.")(NIL NIL "UNEXPECTED_DATA_AFTER_ADDRESS" ".SYNTAX-ERROR.")
That new patch was fixing a case where "User name"@domain address wasn't working.
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: We're on Token Ring, and it looks like the token got loose.
On Fri, 2005-04-08 at 15:26 +0100, Andrew Hutchings wrote:
Apologies I meant '"Full Name" user@domain.com' shows as 'Full Name@MISSING_DOMAIN'
I originally thought that too, but that works correctly with me. Maybe there were some other changes related to it since test60?
Yea, looks like it, ignore me on this one ;)
On Fri, 2005-04-08 at 17:36 +0300, Timo Sirainen wrote:
On Fri, 2005-04-08 at 15:26 +0100, Andrew Hutchings wrote:
Apologies I meant '"Full Name" user@domain.com' shows as 'Full Name@MISSING_DOMAIN'
I originally thought that too, but that works correctly with me. Maybe there were some other changes related to it since test60?
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Support staff hung over, send aspirin and come back LATER.
Right, stop me if I am wrong here as I am no way near an expert on IMAP. As far as I can tell after the EXPUNGE results dovecot gives an EXISTS result, now from what I am observing dovecot is saying the number of mails that were available before the expunge in the exists result after the expunge. OE gets confused by this and invents the missing ones...phew!
Now tell me I'm talking bollox or something :)
Regards Andrew
On Fri, 2005-04-08 at 16:27 +0300, Timo Sirainen wrote:
On Fri, 2005-04-08 at 12:23 +0100, Andrew Hutchings wrote:
This may be a problem with my config file but I am finding that customers (and more importantly my boss) that are using outlook express when using test66/67 (upgraded from test60 + from address patch) are having message reappear after being fully deleted (not just marked) but are unreadable, sometimes blank headers appear too but again no message.
Hmm. And nothing in log file? Were the messages expunged recently (less than an hour ago) or did some older messages also appear? Only OE-related thing that I can think of is this change:
2005-03-14 21:17 Timo Sirainen tss@iki.fi
- dovecot-example.conf, src/imap/cmd-fetch.c, src/imap/common.h, src/imap/imap-sync.c, src/imap/main.c, src/lib-storage/mail-storage.h, src/lib-storage/index/index-sync.c: Renamed oe6-fetch-no-newmail workaround to delay-newmail and changed it to work more like the name says: only newmail notifications are skipped and not only for FETCH command.
But that shouldn't be making expunged mails visible.. Nothing should actually. Unless new messages are getting UIDs from old mails (there is/was a bug like that with mbox, but not maildir AFAIK).
If anyone can find a way to reproduce this I'd like to know.
Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Sysadmin didn't hear pager go off due to loud music from bar-room speakers.
On Fri, 2005-04-08 at 19:55 +0100, Andrew Hutchings wrote:
Right, stop me if I am wrong here as I am no way near an expert on IMAP. As far as I can tell after the EXPUNGE results dovecot gives an EXISTS result, now from what I am observing dovecot is saying the number of mails that were available before the expunge in the exists result after the expunge. OE gets confused by this and invents the missing ones...phew!
That would explain it, but Dovecot shouldn't be sending EXISTS after EXPUNGE unless new mails have arrived. You were able to make it send EXISTS without new mails coming? I kept trying expunges for a while and also sending new mails, but couldn't make it send wrong replies..
An mailbox I just shoved 1422 dummy messages into the new folder (all unread):
in: 91:rrx2 EXPUNGE 92-7xj7 UID FETCH 1454:* (BODY.PEEK[HEADER.FIELDS (References X-Ref X-Priority X-MSMail-Priority X-MSOESRec Newsgroups)] ENVELOPE RFC822.SIZE UID FLAGS INTERNALDATE)
out: 13375:* 1442 EXPUNGE 13376:* 1441 EXPUNGE 13377:* 1440 EXPUNGE 13378-* 1442 EXISTS 13379:rrx2 OK Expunge completed. 13380-* 1440 FETCH (RFC822.SIZE 21776 UID 1454 FLAGS () INTERNALDATE "08-Apr-2005 19:43:24 +0100" BODY[HEADER.FIELDS (REFERENCES X-REF X-PRIORITY X-MSMAIL-PRIORITY X-MSOESREC NEWSGROUPS)] {42}
The message headers appeared again and no messages in the inbox were readable although Dovecot was sending mails that didn't match with the header OE was showing, after deleting OE's local cache it all worked fine again.
On Fri, 2005-04-08 at 22:21 +0300, Timo Sirainen wrote:
On Fri, 2005-04-08 at 19:55 +0100, Andrew Hutchings wrote:
Right, stop me if I am wrong here as I am no way near an expert on IMAP. As far as I can tell after the EXPUNGE results dovecot gives an EXISTS result, now from what I am observing dovecot is saying the number of mails that were available before the expunge in the exists result after the expunge. OE gets confused by this and invents the missing ones...phew!
That would explain it, but Dovecot shouldn't be sending EXISTS after EXPUNGE unless new mails have arrived. You were able to make it send EXISTS without new mails coming? I kept trying expunges for a while and also sending new mails, but couldn't make it send wrong replies..
-- Andrew Hutchings (A-Wing) Linux Guru - Netserve Consultants Ltd. - www.domaincity.co.uk Random BOFH excuse: Collapsed Backbone
On Fri, 2005-04-08 at 21:02 +0100, Andrew Hutchings wrote:
The message headers appeared again and no messages in the inbox were readable although Dovecot was sending mails that didn't match with the header OE was showing, after deleting OE's local cache it all worked fine again.
It's the delay-newmail workaround which breaks it. I'll try to look at it tomorrow.
participants (2)
-
Andrew Hutchings
-
Timo Sirainen