Timo Sirainen wrote:
So far I'm thinking it's Thunderbird bug which should be fixed. Even if Dovecot was responsible in some way for it, it shouldn't be sending negative message sizes.
I've snagged a repeatable case and got a truss of the imap process. I'm inclined to agree with you.
I'll report it to the Thunderbird ppl.
The sequence is (more or less) this:
Client: 10 UID fetch 90309 (BODYSTRUCTURE)
[imapd reads the whole message, then futzes with the dovecot.index file]
Imapd: * 6056 FETCH (BODYSTRUCTURE ("text" "plain" ("charset" "iso-8859-1") NIL NIL "7bit" 796 22 NIL NIL NIL) UID 90309) Imapd: 10 OK Fetch completed.
Client:11 UID fetch 90309 (UID RFC822.SIZE BODY[]<0.10240>)
[imapd read the whole file again - TWICE!]
Imapd: * 6056 FETCH (BODY[]<0> {2064} [entire message] UID 90309 RFC822.SIZE 2064)
[more index stuffing]
Imapd: 11 OK Fetch completed.
Client: 12 UID fetch 90309 (UID RFC822.SIZE BODY[]<10240.-8176>)
Imapd: 12 BAD Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' in '<10240.-8176>'