On Jan 22, 2014, at 8:38 PM, Murray S. Kucherawy <[email protected]> wrote:
> The feature request asks for a way to whitelist deliveries for which there's > "p=reject" and DMARC fails as long as there's a List-Id: or List-Post: field > on a message. This is basically a filter bypass feature that's at the > control of the sender, and it seems like a really bad idea as described. > > There would need to be more to it than just this. Can you develop the idea > more? What should be in the field if it's present? Should it be tied to > something else? > It is not at the control of the sender, it is at the control of the receiver. The receiver needs to enter the IP of where mailing lists are sending from. It is up to the receiver to decide if it should override the policy. This feature is part of the spec where receivers can override the policy and indicate it in the reports.. Because some mailing lists like google-groups send from the same IP as other mail streams, you only want to override the mail that is obviously from a mailing list. The easy indicator I found is the presence of the List-id or list-post header. you could make it more complicated, and tie IPs with the presence of the header and its content (usually the name of the mailing list), but also it is common that several mailing lists are hosted on the same machine, so I don't see the need to make the criteria of surgical precision. The other feature I could open, is to override for well known forwarders (like all these MS-Exchange hosting services out there). Once again at the discretion of the receiver, but it helps when you deal with some third parties, and moving to reject is blocked by a few organizations. _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
