Modify ↓
#264 closed bug (fixed)Email not Base64 decoding
Description
The attached message displays in YAM 2.6p1 as a Base64 encoded block, rather than a correctly decoded message. I've checked it with the latest nightly build (2011-06-07) and the problem still exists in that version. Attachments (1)Change History (6)Changed 2 years ago by anonymouscomment:1 Changed 2 years ago by thboeckel
YAM will not decode the mail because the header is missing the MIME-Version line. The MIME standard requires this line to detect MIME conformant mails.
Please refer to this document: http://www.ietf.org/rfc/rfc2049.txt
I will modify YAM to output a warning and decode the mail nevertheless. But please keep in mind that the bug is located on the sending side to build a non-MIME-conformant mail. YAM is just following the official rules. comment:2 Changed 2 years ago by thboeckel
(In [5710]) * YAM_RE.c: non-MIME-conformant mails without a MIME-Version header line are
comment:3 Changed 2 years ago by anonymous
That works great, thanks. However a message with none of the MIME-Version, Content-Type or Content-Transfer-Encoding headers is also causing YAM to show the warning - I think it should be treating this as a plain non-MIME message as none of the MIME headers are present. comment:4 Changed 2 years ago by thboeckel
I just stripped a mail from all that lines and I get no error with the latest nightly build (26.6.2011). If this is happening for you nevertheless then please provide an example mail. comment:5 Changed 2 years ago by anonymous
It's fine now, thanks. Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber
| ||||||||||||||||||||||||||||



problem message file