Sending from domains which contain UTF-8 or non-ASCII characters

Sometimes, our customers will want to send from domains which contain UTF-8 or non-ASCII characters. For example, I may wish to send messages from domain anitàdomain.com.

 

If a customer tries to add an individual address on such a domain as a Sender Signature, we may accept it. We’re getting inconsistent results with that, though - Safari does not work and Chrome works.

If you try to add a domain like that via Sender Signatures, you will receive an error regardless of the browser:

Results for adding an individual address/Signature on Safari

Results for adding a Domain on Chrome/Safari

 

You can still add the domain directly, but it will need to be added with punycode. You can use a punycode converter

Punycode converter (IDN converter)

 

To turn anitàdomain.com into something like xn--anitdomain-k4a.com - which you can then add as a domain:

You will also need to use the Punycode in the From field because otherwise your request will be rejected:

 

 

When you use a  punycode address, message request will be accepted, and the messages will appear with the punycode From address in Postmark:

 

But in the recipient’s inbox, it will look all pretty with non UTF-8 characters, just as it should (:magic:)