Hello, This is a solution for SPF after forwarding and lists that I've been aware of for a while; I wonder if this is already commonly done?
Forwarding is an action on the receiving end, and can only be solved reliably by the recipient. Notably, a mailbox user could specify addresses that are forwarded to their mailbox. Mailing list subscriptions may be seen as a special form of forwarding. When incoming mail is SPF-validated and the envelope sender does not match the sending MTA address, those forwarded domains can be looked up for the envelope _recipient_ address. Lenient SPF validation would add permission to sending MTAs from these forwarded domains. The result would be that forwarding never breaks, when configured on the receiving mailbox. I am not sure if this is part of the "mark as NOT spam" procedures in common mailbox services, but AFAIK it would fix quite a bundle of problems. I suppose this could also lead to a definition of Lenient DMARC. Cheers, -Rick _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
