Replies from hotmail appear blank.

[cstdenis]

I have multiple users saying replies of replies from Hotmail seem to be coming in blank. A view of message source shows that the data is there, but roundcube seems to be unable to render it (works in ThunderBird?)

Procedure to reproduce:
1. Send a message from roundcube 0.2.1 or 0.3 to Hotmail
2. Reply to that message from Hotmail
3. Reply to the reply in roundcube
4. Reply to the reply in Hotmail
5. View in RoundCube. Message appears blank.

Sample affected message source attached.

[cstdenis]

Sample affected message.

[alec]

Works for me with dovecot. Server issue? Enable imap_debug and check BODYSTRUCTURE response.

[cstdenis]

I am using courier-imap 4.4.1

I'm not quite fluent in IMAP, but If I'm reading it right:

BODYSTRUCTURE ("text" "plain" NIL NIL NIL "8bit" 2630 103 NIL NIL NIL)

I've attached the full debug info.

[alec]

So, we can't do nothing about this. Roundcube rely on bodystructure response, there're tickets to parse raw message in this case, but it's not simple. Server issue.

[cstdenis]

What is the BODYSTRUCTURE provided by dovecot for this message?

[alec]

(("text" "plain" ("charset" "Windows-1252") NIL NIL "quoted-printable" 814 45 NIL NIL NIL NIL)("text" "html" ("charset" "Windows-1252") NIL NIL "quoted-printable" 1421 43 NIL NIL NIL NIL) "alternative" ("boundary" "_733ece41-8f84-4bc8-817a-fc8ba74dd366_") NIL NIL NIL))

[simonp]

I have the same problem with roundcubemail 0.3, dovecot 1.0rc15 (from debian etch) with Hotmail mails. Here's the relevant imap debug lines:

[01-Oct-2009 15:09:13 -0400]: C: FH12 UID FETCH 13618 (UID RFC822.SIZE FLAGS INTERNALDATE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (DATE FROM TO SUBJECT REPLY-TO IN-REPLY-TO CC BCC CONTENT-TRANSFER-ENCODING CONTENT-TYPE MESSAGE-ID REFE
RENCES DISPOSITION-NOTIFICATION-TO X-PRIORITY)])
[01-Oct-2009 15:09:13 -0400]: S: * 4 FETCH (UID 13618 RFC822.SIZE 3155 FLAGS (\Seen) INTERNALDATE "01-Oct-2009 09:52:59 -0400" BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 2154 70 NIL NIL NIL) BODY[HEADER.FIEL
DS (DATE FROM TO SUBJECT REPLY-TO IN-REPLY-TO CC BCC CONTENT-TRANSFER-ENCODING CONTENT-TYPE MESSAGE-ID REFERENCES DISPOSITION-NOTIFICATION-TO X-PRIORITY)] {446}
[01-Oct-2009 15:09:13 -0400]: S: Message-ID: <BAY117-W420E22815526610D1B4327D4D30@phx.gbl>
Content-Type: multipart/alternative;
        boundary="_4ccfc73a-568d-46bc-9688-f36d8c338c40_"
From: =?iso-8859-1?B?TWFydGluIFTpdHJlYXVsdA==?= <tintinto@hotmail.com>
To: nancy tobin <nt@mmebutterfly.com>
Subject: RE: martin demain
Date: Thu, 1 Oct 2009 09:52:57 -0400
In-Reply-To: <2c126036d723b23e000c08fe8f998fdf@localhost>
References: <BAY117-W1113473945C06C4F565A45D4D40@phx.gbl>


[01-Oct-2009 15:09:13 -0400]: S: )
[01-Oct-2009 15:09:13 -0400]: S: FH12 OK Fetch completed.

[cstdenis]

It appears our Barracuda spam firewall may be corrupting the email headers adding a line break before the MIME header. Or maybe Hotmail itself is just sending corrupted email. I haven't had time to fully test yet.

See also this thread in the courier-imap list archives: http://sourceforge.net/mailarchive/forum.php?thread_name=4ABD6C6B.2000608%40smartt.com&forum_name=courier-imap

[LowVoice]

We have exactly the same problems with e-mails from Hotmail. Both versions 0.3 and 0.1.1 have exactly the same problem. Other webmail and e-mail programs view the e-mails correctly.

[alec]

Partially fixed in r3034. Malformed messages are displayed in a raw format.

[LowVoice]

There are a lot of Hotmail users and Microsoft is not going to change their HTML behavior. Isn't there a work around possible, so users can view the e-mail correctly? Other webmail clients like IMP/Horde and Squirrelmail view the Hotmail e-mails correctly.

[alec]

Use smarter IMAP server, like dovecot. Roundcube needs raw message parsing feature, but as I've said it's not simple.

[cahva]

Replying to LowVoice:

We have exactly the same problems with e-mails from Hotmail. Both versions 0.3 and 0.1.1 have exactly the same problem. Other webmail and e-mail programs view the e-mails correctly.

Not exactly. For example Horde/IMP shows the message as raw so it doesnt view it correctly(with courier-imap).