Did you specify SMTPUTF8 on the MAIL FROM command? Is swaks that smart? doesn't look like it. https://github.com/jetmore/swaks/blob/6bc61708489dc9789246e8fe58d32a0ff4fec8f4/swaks#L1055
Our validation cares, though it uses the same error message in either case, so I guess it should say RFC6532 if you do specify an invalid message with SMTPUTF8, but your example isn't doing that. Brandon On Thu, Mar 2, 2023 at 2:36 PM Alex Burch via mailop <mailop@mailop.org> wrote: > RFC 6532 indicates that you can use unicode characters like an umlaut ü > (U+00FC) if the receiving MTA supports SMTPUTF8 extension: > https://www.rfc-editor.org/rfc/rfc6532 > > But when I test this to Gmail its rejected: > > swaks -p 25 -f 't...@acems1.com' --h-From: '"Alex" <kevin@düber.io>' --to > 'acaburchte...@gmail.com' --h-Subject "Umlaut" --server " > gmail-smtp-in.l.google.com" --server="gmail-smtp-in.l.google.com" > > <** 550-5.7.1 [54.242.119.206] Our system has detected that this message > is not RFC > <** 550-5.7.1 5322 compliant: > <** 550-5.7.1 'From' header has non compliant domain name. > <** 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has > been > <** 550-5.7.1 blocked. Please visit > <** 550-5.7.1 https://support.google.com/mail/?p=RfcMessageNonCompliant > <** 550 5.7.1 and review RFC 5322 specifications for more information. > x12-20020a0ce24c000000b0053428216ed9si277098qvl.216 - gsmtp > > Does Gmail not support RFC 6532 which states a unicode character should be > allowed in the From header? The bounce refers to RFC 5322 which is prior to > 6532. So maybe they are still strictly respecting the older 5322? > > It does work if I use punycode: aburch@ke...@xn--dber-0ra.io > > Which aligns with Google docs here that say "Your domain name only has > numbers, letters, dots, or hyphens" > https://support.google.com/mail/forum/AAAAK7un8RUe15zAgzGbc4/?hl=en&gpf=%23!topic%2Fgmail%2Fe15zAgzGbc4%3Bcontext-place%3Dforum%2Fgmail > > But here they also say "Gmail (and shortly, Calendar) will recognize > addresses that contain accented or non-Latin characters. This means Gmail > users can send emails to, and receive emails from, people who have these > characters in their email addresses." > https://blog.google/products/gmail/a-first-step-toward-more-global-email/ > > So which one is it?!? Do they support unicode characters in a domain/From > header? In reality no, but they seem to hint that they intend to. > > Thanks, > Alex > > > -- > > Alexander Burch > ActiveCampaign / Senior Deliverability Engineer > abu...@activecampaign.com > 1 North Dearborn St Suite 500, Chicago IL, 60602 > <https://www.facebook.com/activecampaign> > <http://www.twitter.com/activecampaign> > <https://www.linkedin.com/company/activecampaign-inc-> > <https://plus.google.com/107063868317743606466> > > <https://www.activecampaign.com/sig/?u=aburch&c=1> > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
