Referring to http://mla.libertine.org/tmda-users/200201/msg00311.html
This is a temporary fix until TMDA supports encoding of multi-lingual headers, but I think it will work for you. The problem is that the Subject line you are using in your confirm_request.txt is not RFC 2047 encoded. When TMDA processes the template, it too, is not doing any encoding of that header. The result is the confirmation message goes out with an 8-bit data in its headers which is not RFC compliant. Many sites automatically refuse such messages at the SMTP level because it's often a clue that the message is SPAM. So, what you have to do is include a charset _encoded_ Subject directly in your TMDA template. It will remain encoded when sent out, and the recipient's MUA will handle the decoding of the header. Plus, the message headers will be RFC-compliant 7-bit ASCII. Here's an example from my confirm_request.txt: From: "%(FULLNAME)s" <%(recipient_address)s> Subject: Please confirm your message / =?iso-2022-jp?b?GyRCQ2U/LjI7JHJKUTk5JDckPyQkGyhC?= When the confirmation request arrives, the Subject is now nice and decoded (see attached screenshot). An easy way to get the right encoded string to use is to simply send yourself a message in Gnus with the same Subject as you want to use in your template. Gnus will do the encoding, and then after you send it, look at the raw text with a pager like `less' and cut-and-paste the encoded string from the Subject. Then insert this into your template. Let me know how this works for you.
iso-2022-jp.png
Description: PNG image
