Open
Bug 461293
Opened 16 years ago
Updated 2 years ago
IMAP log reports "PARSER:Internal Syntax Error on line: %s:"
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: nelson, Unassigned)
References
Details
SM trunk nightly 20081009. While studying the IMAP log for bug 460085, I found an error in it. Apart from the badly formatted log entry, I think this indicates a bug either in TB or the server, but I don't know which. I'd appreciate an IMAP expert's opinion on this bug. The log file contains entries like these: (shortened here to fit) : 28 STATUS "Bulk Mail" (UIDNEXT MESSAGES UNSEEN RECENT) : * STATUS Bulk Mail (MESSAGES 0 RECENT 0 UIDNEXT 1 UNSEEN 0) :PARSER:Internal Syntax Error on line: %s: * STATUS Bulk Mail (MESSAGES 0 RECENT 0 UIDNEXT 1 UNSEEN 0) : 29 logout : 28 OK STATUS completed. I'm guessing that the problem is that the parser expects the words Bulk Email to be enclosed in quotes, just as they were when the client sent them. Whose bug is that?
Updated•16 years ago
|
Version: 1.9.0 Branch → Trunk
Comment 1•16 years ago
|
||
(In reply to comment #0) > : 28 STATUS "Bulk Mail" (UIDNEXT MESSAGES UNSEEN RECENT) > : * STATUS Bulk Mail (MESSAGES 0 RECENT 0 UIDNEXT 1 UNSEEN 0) > :PARSER:Internal Syntax Error on line: %s: * STATUS Bulk Mail (MESSAGES 0 > RECENT 0 UIDNEXT 1 UNSEEN 0) Your guess is right. As seen in Status command(28 STATUS ...) issued by Thunderbird, mail box name have to be quoted by double-quotes when space character is included in mail box name. However, your server returns mail box name of Bulk Mail without quoting. See RFC 3501 ( http://www.faqs.org/rfcs/rfc3501.html ) => Server's bug, or server side incorrect/inappropriate configuration.
Reporter | ||
Comment 2•16 years ago
|
||
Thanks, Wada, I suppose I could ask that something be done about that "%s" in the log, but it doesn't seem to have hurt our ability to diagnose this problem. Feel free to mark this bug invalid.
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•