----- Original Message ----- > From: "J. Gomez" <[email protected]> > That is why, in my view, DMARC's p=reject has to either be reliable to be > relied on, or be suppressed from DMARC's formal specification if it is going > to mainly be equal to p=do-whatever. >
when you see a p=reject and DMARC tells you, you should bounce the email, then just bounce it. Why? 1) there are reports to tell the sender why you bounced the email. And it should get the bounce too. If it is not what the sender wants, he has all the tools to assess if it was important for the receiver to receive this message or not and what can the sender do to change that. 2) Mailing lists should be able to differentiate between an Hard bounce and a Soft bounce (by now). http://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml is 7 years old now. If you do anything else, it is because you want to be nice to the sender. (pulling leg here) _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
