#411 reply to japanese encoded email fails with delivery error

closed-fixed
Jamie Cameron
Read Mail (122)
5
2011-08-21
2011-08-15
Neil Chittenden
No

Using Usermin 1.470, configured with the language in en.utf-8 and to send email using utf-8.

On receiving a iso-2022-jp encoded message (which displays fine), I then choose reply to all. Some of the email addresses in the CC section are preceded by Japanese characters. On viewing the page encoding, the main frame is UTF8 as expected and the inner frame for replying to the email shows an encoding of ISO-2022-JP. This is all fine and displays correctly.

However, when sending this email, the output from looks a bit mangled and I receive an undelivered email message from the mail server with the following details:

Final-Recipient: rfc822; =?ISO-8859-1?Q?=20?='?$B9b@%?
Action: failed
Status: 5.1.3
Diagnostic-Code: X-Postfix; bad address syntax

Output from send:
Sending mail to User One <user1@someplace> , "$B%A%$%O%-(B"<user2@someplace> , "$B%&#61;%R%3%&#61;%R%3(B" <user3@someplace> ..

.. done.

The email is only sent to recipients listed before the ones with japanese encoded characters.

Discussion

  • Jamie Cameron
    Jamie Cameron
    2011-08-15

    That sounds like a bug ..

    Could you send me email that displays this problem at jcameron@webmin.com , so I can see how Usermin is mis-parsing it?

     
  • Have sent an email that displays the issue as requested.

     
  • Jamie Cameron
    Jamie Cameron
    2011-08-16

    Thanks for the email .. I think the issue is Usermin is encoding japanese input in the wrong way, causing corruption of the address.

    Could you also send me email from the same mail client that has japanese text in the body?

     
  • Now sent that email as requested. You may have already noticed but in the original (iso-2022-jp encoded) email message source, the email addresses start with =?ISO-2022-JP; in the message source from the reply generated by usermin, they start with =?ISO-8859-1. I don't know that much about email structure or encodings but this looks a bit suspicious.

     
  • Jamie Cameron
    Jamie Cameron
    2011-08-18

    Thanks, that was helpful .. I am working on a fix now.

     
  • Jamie Cameron
    Jamie Cameron
    2011-08-21

    This will be fixed in the next Usermin release..

     
  • Jamie Cameron
    Jamie Cameron
    2011-08-21

    • status: open --> closed-fixed