VM

  1. Bug #612111
  2. Comment #13

Comment 13 for bug 612111

Revision history for this message
Arik (akwm) wrote : [Bug 612111] Re: digest message improperly handles boundary

Uday Reddy writes:
 > Arik writes:
 >
 > > Okay. gmail is getting this wrong then for digest messages, I will
 > > file a bug report.
 >
 > Gees, I didn't realize it was gmail-generated. Thought NPR was
 > sending it through some custom program.

No, the NPR feed I generated, the problem with gmail is if you forward
multiple messages (uses digest) then gmail doesn't recognize the
encoding properly. This is probably what led me to interpret the rfc
that way. But now, after doing some tests, it looks like gmail's
problem is that for digest messages it does not properly assume that
the content-type is "message/rfc822" like it should for
"multipart/digest" when it is not specified.

I gathered this by sending utf encoded messages to gmail in the normal
VM way (no mime-header part) and then I explicitly added the
"message/rfc822" header at which point gmail displayed the messages
properly.