This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Previous message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Next message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Hungenberg
th at cert-bund.de
Wed Nov 20 13:01:02 CET 2019
On 19.11.19 15:21, Michele Neylon - Blacknight wrote:
> If your email client or server can’t handle UTF-8 then doing the punycode conversion is unlikely to help
Based on our experience, it does help.
If messages bounce because the recipient's MTA does not support SMTPUTF8,
sending the message to the IDNA representation of the recipient address usually works.
But I have also seen cases where the recipient's MTA supported SMTPUTF8 correcty
but some MTAs or services like spam filters on the transport way did not and thus
screwed up delivery of the message.
- Thomas
CERT-Bund Incident Response & Malware Analysis Team
- Previous message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Next message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]