#364 Handling of GB2312 Base64 Encoded Message - MailMate

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#364 ✓bluesky

Handling of GB2312 Base64 Encoded Message

Reported by Ryan Erwin | March 15th, 2013 @ 01:02 AM

Not sure if you're planning to add an "encoding" menu to MailMate, or if there's a way to write an Event-Driven Script that can be connected to a keyboard shortcut to adjust the encoding.

Anyway, here's an example of a message that works just fine in Mail.app and Mac QuickView, but isn't readable in MailMate.

I've attached a screenshot of the Mailmate rendering, the QuickView rendering, and the RAW message source.

Comments and changes to this ticket

benny March 15th, 2013 @ 07:35 AM
On Lion I get the same rendering in Apple Mail (and Quick Look) as in MailMate. Looking at the raw message this is because no encoding is specified for the message. In other words, it works as expected.

If I change the text encoding in Apple Mail then the filename for the attachment is still not correct.

I don't have any immediate plans of adding an “Encoding” menu. Corrupted messages like the above seem to be very rare. Actually I think this is the first time a user reported an encoding error which cannot be fixed by making a workaround.

Is this a legitimate message or a spam message?
benny October 10th, 2013 @ 09:47 AM
- State changed from “new” to “bluesky”
Cleaning up old tickets. I'll mark this one as bluesky at least until it appears to be a general problem for users.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.