It's actually not even enough to check when you subscribe, though that will help keep the user from being surprised later. But you also have to check every time a message is posted to the list, because anyone's domain could have changed to p=reject recently.
And anyway, yes, the IETF considered that and decided, as you say, to try to be more inclusive. But we've seen problems caused by the From rewriting also, related to difficulties in replying... it's not benign. Barry On Tue, Jul 11, 2023 at 4:30 PM Tero Kivinen <kivi...@iki.fi> wrote: > > Barry Leiba writes: > > > 2) As others have observed, the mailing list problem is > > > exclusively an evaluator error. An evaluator's job is to allow > > > safe and wanted messages while blocking unsafe or unwanted > > > messages. > > > > I disagree. As I and others have observed, those creating the problem > > are the ones who are using p=reject in a way that it was not intended > > to be used. > > If we simply want to "fix" the mailing list issue, the mailing lists > could simply refuse any subscription attempt from address which > publishes p=reject, and say that your email address is not compatible > with mailing lists in general, use some other address when sending > emails to mailing list. > > On the other hand mailing list adminstrators usually try to include > everybody, and not block people if they can cope with them, and thats > why they do From address rewriting etc instead of just rejecting > subscription requests. > -- > kivi...@iki.fi _______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc