On Wed, Apr 1, 2020 at 5:32 PM John Levine <[email protected]> wrote: > In article <[email protected]> you write: > >To decide for an authserv-id whether to pull sub-domain from 5321 or > >6531, one needs to know if the message is internationalized. But to > >obtain that information, one must have parsed all message header fields, > >per 6531 sec 3.6, including A-R, that is still waiting to be parsed. > > In systems that keep ASCII and EAI mail separate, that info will be in > the metadata, whether it arrived in an SMTP session with the SMTPUTF8 > option. >
Does anyone implement it that way? We just upgraded our parser to handle EAI mail, and the parser returns requested data in UTF8, decoding 5322 mail or going straight from 6532 mail as necessary, with specific accessors needing to know what the possible encodings could be. We then check when we go to send mail whether we should specify SMTPUTF8 on the output.. as for input... We see plenty of mail transferred without SMTPUTF8 that contains UTF8 (or other 8-bit characters, but the majority of that became UTF8 probably close to a decade ago), and we just handle it. Unfortunately, everybody thinks they can just make their own emali messages because its a text-like format, and they're very often wrong. Brandon
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
