On 2022-06-02 05:08, Alessandro Vesely wrote:
Sorry, but this is not an SPF issue. David's message arrived at IETF
with a helo name of wforward1-smtp.messagingengine.com, which has a
correct SPF record, and a DKIM signature by d=messagingengine.com.
Perfectly authenticated, then, except for alignment.
Does SPF care about EHLO names when there is a non-null RFC5321.Mail?
SPF should be able to handle this situation using macros anyway:
bustos.name. IN TXT "v=spf1 include:%{l}._spf.bustos.name -all"
david._spf.bustos.name. IN TXT "v=spf1 redirect=david's-email-provider"
The registry would need to allow users to define
"david's-email-provider", but they already need to allow configuration
of forwarding addresses and nameservers, so this seems pretty doable.
I don't think you'll be able to get aligned DKIM though, so recipients
who forward their mail will be broken but forwarding is already broken,
this is just Yet Another Example.
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc
