I keep getting "PARSER:Internal Syntax Error" in my IMAP log. I've now done some debuging and found out it's due to mails that are having a NULL char (\x0) in them. Mozilla IMAP'ning simply dies. I can reproduce this on my InterMail IMAP server but not on Exchange. This bug causes Mozilla to stop IMAP for the current account, meaning clicking on a mail does not fetch the mail but just display the mail as empty = potential dataloss. I can sent a test mail if you tell me which mailaddress to sent to. 1360[2d9c448]: imap.mail.dk:S-INBOX:PARSER:Internal Syntax Error: %s: FLAGS (\Recent \Seen)) Build 20011126
I can also provide you with IMAP access to my IMAP server so that you can see the problem yourself. 100% Reproduceable...
imap messages aren't allowed to have nulls in them, right? If the server is actually returning a null byte, that sounds like a server problem.
IMAP messages are indeed not allowed to have NUL octets in them. See RFC 2060 sections 4.3.1 and the definition of msg_att in section 9 (it goes down to CHAR8, which prohibits NUL).
I can reproduce this problem by using Henrik InterMail vM.4.01.03.23 server. But, Scott, can you confirm this bug is server problem based on David & John's comments?
If it's a server problem, let's mark invalid or wontfix, unless you think there's something we could do to ignore the null and still display what we can of the message.
Status: NEW → ASSIGNED
I'd say mark it invalid.
related to bug 115179? that bug has a patch
QA Contact: huang → meehansqa
Summary: Getting "PARSER:Internal Syntax Error" when mail contains NULL char (\x0) → InterMail vM.4.01.03.23: Getting "PARSER:Internal Syntax Error" when mail contains NULL char (\x0)
(In reply to comment #6) > I'd say mark it invalid. Is this still a problem (comment 7)? If so, should failure of server necessarily cause failure in client? Also "Internal Syntax Error": * Bug 109321 * Bug 133689
Assignee: mscott → bienvenu
Status: ASSIGNED → NEW
QA Contact: meehansqa → grylchan
David, other reported bugs are closed except Henrik's - hasn't responded so perhaps he doesn't see this anymore. Is there a test message? Any thoughts?
It's illegal for the server to return embedded nulls - I vaguely remember some fixes going in to handle them anyway, I think from timeless, but I can't remember if it was for IMAP or POP3...
i can't remember them, but my memory is shot and i'm sure this would have been years ago. did someone file a bug against intermail? we definitely should have a reference to their bug database.
marking invalid - it's a server error in any case. I haven't heard other reports about this, so maybe it's dealt with in our code, or fixed w/ InterMail.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.