On 4/13/2023 11:14 AM, Barry Leiba wrote:
There's no need for a signal here: the MLM can simply check the sending domain's DMARC policy when a new post comes in, and preemptively reject it if the policy is "reject". The IETF considered doing that and ruled it out because it would mean that users with yahoo.com addresses (and others) could then not participate in IETF mailing lists without changing addresses.
Code change where?  In the MLS or some post scripting code?

I think that was the wrong decision, but we decided on the ugly "from" alteration instead.

Code change anyway. No way around this code change - a direct MLS change or MLM low code script add-on/change. My MLS checks it's entry points for restrictive DMARC domain; subscription and submissions.

I still think that outright refusal of posts from p=reject domains is a good approach and I wish it were used more, but most MLMs that are willing to put in a change to address this seems to prefer not to punish the sending domains users for the excesses of the domain management.

+1.

It can only be considered more with key cogs support and promotion to their industry/trade support peers. Iow, Editors SHOULD support/champion their RFC work like ATPS and DMARC. Many ideas and concepts from DSAP merged from WG work. DMARC is a collection of all the past work with reporting. But it needs DSAP policy ideas and ATPS concept to help bring some steady state to transporters. DMARCbis p= should be describing the failure handling not restricting the evaluation of a failure. This will provide the tools to define the nine possible 1st vs 3rd party signers. MLS needs to support this. The MLM operators need to support it too. Of course, the MLS/MLM can use Local Policy to override at its own risk especially when DMARCBis offers nothing to resolve this problem. But it can easily fit in too and see where it goes.


--
Hector Santos,
https://santronics.com
https://winserver.com



_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Reply via email to