#223 new

Encoding of non-ascii characters in subject

Reported by mariow | January 24th, 2012 @ 07:40 AM

When a subject line contains non-ascii characters, Mailmate only encoded the work containing the special character, e.g. for the line "Test für Umlautmails" it would send
Subject: Test =?utf-8?q?f=C3=BCr?= Umlautmails
while most mail clients would encode the whole line
Subject: =?UTF-8?Q?Test_f=C3=BCr_Umlautmails?=

I understand that the encoding used by Mailmate is legit, but I still have problem that some (one?) recipient does not receive it correctly. Is there any (hidden?) setting to change this to encoding the full line?

Comments and changes to this ticket

  • benny

    benny January 24th, 2012 @ 02:02 PM

    The MailMate style is more readable in my opinion, but if there are clients out there unable to handle it then I guess I have to change it. Do you know the name of the receiving email client?

    (I'm going to hate seeing my own name in raw emails.)

  • mariow

    mariow January 24th, 2012 @ 02:28 PM

    I absolutely agree, the way Mailmate encodes it is more readable and saves a few bytes on longer subject lines. My problem right now is with followup.cc, a service that generates followup reminders when I CC them in my mails.

    Basically what I was hoping for was a way to change this behavior with some hidden switch - as long as it does not come up as a problem in a major mail client I think changing the logic for everyone would be too much.

  • benny

    benny January 24th, 2012 @ 04:27 PM

    • State changed from “new” to “resolved”

    Thanks for the example. Do you know if this service has any problems with address headers? These are never encoded in full. The name or part of the name may be encoded, but the address is never encoded.

    For now I added the following for subject lines, but I don't guarantee I'll keep it if it is just to handle a single buggy website:

    defaults write com.freron.MailMate MmEncodeFullSubjectLines -bool YES

    Users with other examples of services or clients which fail to handle encoded words (while handling encoded lines) are welcome to add a comment.

  • mariow

    mariow January 26th, 2012 @ 01:18 PM

    Thanks a lot for the quick fix! Is this going to be in the next unstable release? I just upgraded to 2702, but that does not seem to have the fix?

  • benny

    benny January 26th, 2012 @ 01:24 PM

    The latest test builds have been unstable for some users and I'm still trying to figure out what the problem is. You are welcome to try the following two builds and tell me how it works for you (they both include the encoding workaround):


    They are not available via Software Update. (And they currently produce a lot of debug output.)

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.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket