John Leslie wrote:
For one example, a BATV signature of the 2821.MailFrom entirely
passes the buck (of responsibility for validity) to the BATV signer.
BTW, could "you" (anybody interested in BATV) please check from time
to time that EAI with its UTF-8 local parts is still compatible with
BATV ? So far I think anything is fine wrt SPF, but I'm not sure
wrt SRS, SES, and BATV, let alone DKIM. Maybe the algorithm has to
be updated, supporting UTF-8 local parts as input on the BATV sender
side, and as output on the BATV DSN receiver side.
Frank