[Tickets #12441] Re: JS error during mailbox loading
noreply at bugs.horde.org
noreply at bugs.horde.org
Tue Jul 9 21:27:18 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/12441
------------------------------------------------------------------------------
Ticket | 12441
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | JS error during mailbox loading
Queue | IMP
Version | 6.1.2
Type | Bug
-State | Unconfirmed
+State | Feedback
-Priority | 2. Medium
+Priority | 1. Low
Milestone |
Patch |
-Owners |
+Owners | Michael Slusarz
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2013-07-09 15:27) wrote:
No, that shouldn't matter. *Our* code should handle it. The issue is
if the IMAP server sends something strange.
I can verify I can see that message fine when using Dovecot 2.2.4.
The pertinent part of the IMAP debug log:
C: 7 UID FETCH 1 (ENVELOPE FLAGS RFC822.SIZE BODY.PEEK[HEADER.FIELDS
(IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)])
S: * 1 FETCH (UID 1 FLAGS (\Recent) RFC822.SIZE 534 ENVELOPE ("Sun, 8
Jan 2012 14:31:46 -0500" {103}
S: [LITERAL DATA: 103 bytes]
S: (("=?US-ASCII?Q?Keith_Moore?=" NIL "moore" "cs.utk.edu"))
(("=?US-ASCII?Q?Keith_Moore?=" NIL "moore" "cs.utk.edu"))
(("=?US-ASCII?Q?Keith_Moore?=" NIL "moore" "cs.utk.edu"))
(("=?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?=" NIL "keld" "dkuug.dk")({5}
S: [LITERAL DATA: 5 bytes]
S: NIL "blah" "example.com")) (("=?ISO-8859-1?Q?Andr=E9?= Pirard" NIL
"PIRARD" "vm1.ulg.ac.be")) NIL NIL
"<803734518.1326051106099.JavaMail.root at example.com>")
BODY[HEADER.FIELDS (IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)] {2}
S: [LITERAL DATA: 2 bytes]
S: )
S: 7 OK Fetch completed.
The "LITERAL DATA 5 bytes" is the "Bläh" text (3 single-byte chars + 1
multibyte char = 5 octets"
I'm wondering if your IMAP server is sending the Bläh in a string
instead of a literal. Which would mean your IMAP server is broken.
Need an IMAP log to verify.
---
To further debug this issue, we need details of the IMP -> IMAP/POP
communication.
To enable debugging, see instructions contained in
imp/config/backends.php (the 'debug' config parameter).
Debugging should not be enabled on a production server, Attach/post
only the portion of the log that directly deals with the problem
reported (it may be simplest to clear the log file and then perform
the event that causes the error).
More information about the bugs
mailing list