>>> It's the one you found. If the authserv-id has a non-ASCII UTF-8 character, >>> it's invalid under 5321 and valid under 6531. >> >> I thought we established that as soon as the authserv-id has non-ASCII >> UTF-8 characters, the mail is automatically - by definition - a 6531 mail: > > Sorry if it seemed like I said that. It's either a potentially valid > EAI message or a definitely invalid ASCII message. If your system > doesn't handle EAI mail, it's invalid.
Ok, that is definitely an external factor, isn't it? The information, if the system which processed the email, handles EAI, is not contained within the A-R header. Is the information even available in the DATA portion of an SMTP transaction? Can one look inside an .eml file and decide if that email has been processed by an EAI capable system? > If there are bytes with the > high bit set but they're not a UTF-8 sequence, or they're not a UTF-8 > character allowed in an authserv-id it's invalid even if you handle > EAI. That part is fine, because this is decidable from the A-R header itself. _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
