close
Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#264 closed bug (fixed)

Email not Base64 decoding

Reported by: chris@… Owned by:
Priority: undecided Milestone:
Component: undefined Version: nightly build
Severity: major Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

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)

msg.lha (2.7 KB) - added by anonymous 3 years ago.
problem message file

Download all attachments as: .zip

Change History (6)

Changed 3 years ago by anonymous

problem message file

comment:1 Changed 3 years ago by tboeckel

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 3 years ago by tboeckel

  • Resolution set to fixed
  • Status changed from new to closed

(In [5710]) * YAM_RE.c: non-MIME-conformant mails without a MIME-Version header line are

no longer displayed as raw 7bit ASCII text but will be decoded as usual.
However, a warning about the missing header line will be presented to give
the user a hint about that fact. Non-MIME-conformant mail clients (like that
Android thingy) are becoming more and more common these days and it is
better to have a possibly malformed mail text than a raw base64 dump. This
closes #264.

comment:3 Changed 3 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 3 years ago by tboeckel

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 3 years ago by anonymous

It's fine now, thanks.

Add Comment

Modify Ticket

Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
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

  • chris@…(Reporter)