Notification e-mails unreadable, unsendable.

[polarfox@…]

When trying to send notification E-mail, half of them get rejected, and all are un-readable.

headers are so badly damaged that sendmail adds default mail domain after email, I'm suprised it got trough.

could someone help?

[polarfox@…]

fucked up e-mail source

[polarfox@…]

side note, this really prevents us from using trac to anything else than browsing subversion tree.

[polarfox@…]

I don't understand python, so I wont go there, but looking at the mail, I think this is some serious overencoding and re-encoding shit :)
From: =?utf-8?q?Taajama_=3Cpolarfox=40taajama=2Efi=3E?=@smtp.taajama.com
'=40' there is '@', and so on, I think something is wrong way the mails are encoded.
Having done webmail software with php I've done many mistakes with encodings myself too, but this looks like easy to fix? maybe I should shut up and learn python.

[polarfox@…]

After few hours hammering my head to the wall, I think I have a solution, DO NOT USE MIMEText :)

I found others saying that unicode in headers doesn't work like it should.
(​http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/MailFormatting)

And really, those mail headers do blow up when using utf-8 to encode fields like: date, content-type, MIME-Version and email address parts of recipients and senders. there might be others but those are required for things to work ok.

[polarfox@…]

I'm not sure, but these might work with postfix.
most e-mail clients do not parse headers that I listed that are encoded, but our webmail software does.
sendmail doesn't work right with encoded addresses either.
As you can see from my comments, this is really important to us, and I'm still on the case.

[Norbert Unterberg <nunterberg@…>]

I've added milestone 0.9 so the ticket does not get lost ;-)

[cmlenz]

Patches would be welcome for this issue ;-)

[eblot]

(I've started working on this one)

[eblot]

First attempt to improve notification with MIME content

[eblot]

Mikko (polarfox@…), could you give a try with the patch I've attached to see whether it helps resolving this issue ?

The idea behind this patch is the following:

As we deal with MIME encoded data (utf-8/base64), a multipart MIME message is reated where only the mail body (text) and some headers are encoded, rather than creating a 'fully' encoded email, which seems to cause troubles with some kind of SMTP server.

Thanks. (patch built from [2391])

[eblot]

[2416] should address this issue. Can you give it a try ?

[eblot]

Other patch with better header encoding

[eblot]

Polarfox, I've added another patch (based en [2391] as well). Could you also give it a try, if the [2416] changeset does not solve the header issue ?

Also try replacing "BASE64" with "QP" to check if the server has less trouble with quoted printable encoding.

[polarfox@…]

add's some glue to eblot's patch that makes things work. ugly patch, but works for me.

[eblot]

Should be addressed by [2799]