On Fri, Jun 27, 2014 at 04:16:10PM -0700, Dave Crocker wrote: > That said, yes, the ruleset for IETF mailing lists probably needs > tweaking, given the unusual nature of our content, with respect to > spam/anti-spam work.
There's no need to run SpamAssassin on the IETF lists: simply configure Mailman to reject all traffic from non-members and let the list-owner add other needed addresses on an ad-hoc basis. (Mailman will by default hold traffic sent from addresses it doesn't recognize. The interface then allows the list-owner to either discard, accept or reject those messages. Simultaneously, it allows the list-owner to decide what to do about the originating address, and one common choice is to add the address to the list which are permitted to send traffic. This avoids involving the list-owner again when more traffic is received from the same non-subscribed address. I've used this mechanism for many years and it works efficiently and beautifully, particularly with people who use multiple addresses to end traffic to mailing lists.) ---rsk _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
