1106890 - Error in IMAP command UID FETCH: Invalid BODY[..] parameter: Unexpected data after ']'

Status: RESOLVED INVALID

(Thunderbird :: Untriaged, defect)

Description

[koonkii]

Attachment: thunderbird-log.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141106120505

Steps to reproduce:

1. Start up thunderbird
2. Upon start, client fetches email headers (without body) from IMAP server.
3. Click on email to read
4. See lots of errors in notification
5. Email preview panel is blank.


Actual results:

I saw lots of errors in the notification. Began logging them to file a bug report (attached).

Also tried the latest beta v34, still running into the problem.


Expected results:

Email loads in the preview panel.

Comment 1

[koonkii]

Attachment: thunderbird-error.png

Added screenshot of the error notification.

Comment 2

[WADA:World Anti-bad-Duping Agency]

(In reply to koonkii from comment #0)
> thunderbird-log.txt

Log for error is as follows. "Unexpected data after ']'" is <nnnnnn.65536> where nnnnnn=Offset and 655534 is length.
> 2014-12-02 21:49:03.219000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:SendData:
>       16 UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<262144.65536>)
> 2014-12-02 21:49:03.505000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:CreateNewLineFromSocket:
>      16 BAD Error in IMAP command UID FETCH: Invalid BODY[..] parameter: Unexpected data after ']'
> 2014-12-02 21:49:03.510000 UTC - 1768[12989140]: FetchMessage peek: curFetchSize 65536 numBytes 65536
> 2014-12-02 21:49:03.510000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:SendData:
>      17 UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<327680.65536>)
> 2014-12-02 21:49:03.794000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:CreateNewLineFromSocket:
>      17 BAD Error in IMAP command UID FETCH: Invalid BODY[..] parameter: Unexpected data after ']'
> 2014-12-02 21:49:03.800000 UTC - 1768[12989140]: FetchMessage peek: curFetchSize 65536 numBytes 65536
> 2014-12-02 21:49:03.800000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:SendData:
>      18 UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<393216.65536>)
> 2014-12-02 21:49:04.084000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:CreateNewLineFromSocket:
>      18 BAD Error in IMAP command UID FETCH: Invalid BODY[..] parameter: Unexpected data after ']'
> 2014-12-02 21:49:04.089000 UTC - 1768[12989140]: FetchMessage peek: curFetchSize 65536 numBytes 65536
> 2014-12-02 21:49:04.089000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:SendData:
>      19 UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<458752.65536>)
> 2014-12-02 21:49:04.372000 UTC - 1768[12989140]: 10d6a800:mail.koonkii.com:S-INBOX:CreateNewLineFromSocket:
>      19 BAD Error in IMAP command UID FETCH: Invalid BODY[..] parameter: Unexpected data after ']'

(Q1) Is you server correctly configured?


(Q2) Many logs are not provided by you. "xx UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<NNN.65536>" where NNN=0, NNN=65536, ..., should exist.
Was same error returned from your server for "xx UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<0.65536>"?
Or different error for first "xx UID fetch 108812 (UID RFC822.SIZE BODY.PEEK[]<0.65536>"?
If so, what error response? Following?
   Response of "NO" from server, but Tb requests BODY.PEEK[]<65536.65536>, so "BAD" response from server.

(Q3) Do you see your problem with mail.imap.mime_parts_on_demand=false? 
(default is true. if false, BODY.PEEK[] only is perhaps used by Tb. However, BODY[TEXT]<0.2048> is issued by Biff...)

Another concern.
> 2 ENABLE CONDSTORE

(Q4) Do you see your problem with Tb's CONDSTORE  support disabled? (read bug 912216, please)

Comment 3

[koonkii]

Hi there WADA,

Q1) I would assume so, I have had no problems with it until today. I asked the people sending emails to me to send it again and it worked properly the second time around.

Q2) I trimmed the logs, wasn't sure what was relevant. I can upload more if you need, I just need to spend some time checking if there is any personal information in it.

Q3) I'm not quite sure what this means.

Q4) I'm not sure what this means either, but my email isn't running off Google's Gmail.

Sorry, I know it's not helpful but it's the first time I've seen these words

Comment 4

[koonkii]

Hi guys,

After system testing, I determined it was my antivirus ESET that was messing with my IMAP emails.

If I disabled email scanning, Thunderbird was able to load the emails which was previously causing errors.

Feel free to close the ticket if needed.

Comment 5

[Frank Iannarilli]

Same problem for me too.  (ESET scanning).  
Problem manifested, I thought, due to S/MIME issues. 
Opening emails with large attachments would cause TB to 
go into max CPU usage, needing to kill process.  Problem
would not occur with small S/MIME attachments. 
The problem seemed to be dependent on connection quality;
at work, I could open medium-sized attachments okay whereas at home,
those would cause the problem.  

Cheers