On Fri, Feb 13, 2015 at 7:46 AM, Steve Atkins <st...@blighty.com> wrote:
>> Such is life. Personally, I have no problem mangling or blocking messages >> from users using a domain with a restrictive DMARC policy as needed. > > Mangling encourages bad behaviour. Blocking discourages it. Blocking, aka rejecting participation from legitimate users because of their domain, might be easy for hobbyists to stomach, but is not always the best path for an existing group or enterprise. It leaves the affected end users feeling hurt and caught in the middle in a scenario they can't easily change. (They certainly can't force AOL to change DMARC policy and they may have legitimate reasons as to why they don't wish to change mail providers.) It doesn't seem to me to be a reasonable solution for everyone. That may be why Yahoo Groups and Google Groups both chose to implement header changes -- instead of telling subscribers to go away. For folks looking for a point of view other than "just lock those users out," I'd suggest checking out some of my suggestions. Looks to me that these align with the paths taken by Yahoo and Google (and maybe Mailman, too). http://www.spamresource.com/2014/04/run-email-discussion-list-heres-how-to.html And if you're looking for more in depth on DMARC policy issues like this overall, I'd suggest looking here: http://www.spamresource.com/search/label/dmarc Cheers, Al -- Al Iverson | Minneapolis, MN | (312) 725-0130 aliverson.com | spamresource.com | @aliverson _______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop
