On Fri, Feb 19, 2016 at 03:23:15PM +0100, Olaf Hering wrote: > Its Friday, so I ran it in gdb. The bug is in mutt_decode_base64. After > the base64 stream ends, a newline comes. Then the '-- ' and the > remaining msg.
There's a reason all three mail clients got this wrong... AFAICT, the bug is in the data; I believe the message is malformed, probably due to the action of the mailing list management software, by the looks: > # X-MIME-Notice: attachments may have been removed from this message It's been a long while since I was very familiar with the relevant RFCs, but I'm fairly certain that the base64 data should not be mixed with any plain text (the mailing list unsubscribe info) in the same message part; if you're going to mix base64 with non-base64 data, the message should separate the two with MIME part headers. Mutt probably could do a better job of handling this, but all it really need do is complain that your message is b0rked. Mailing list management software should never mangle messages. When it does so, at best they thwart the intentions of the sender, and at worst it produces broken messages. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgpbyIILPut4N.pgp
Description: PGP signature
