>________________________________________ >From: Reindl Harald <h.rei...@thelounge.net> >Sent: Monday, May 25, 2015 7:23 AM >To: users@spamassassin.apache.org >Subject: Re: Block mailing lists
>Am 25.05.2015 um 14:17 schrieb Lorenzo Milesi: >>> There are inherit dangers of what you want to do, but if you're the only >>> mail >>> user, then you know and accept the risks, if you host mail for others, >>> under no >>> circumstances should you do any of this with 100% agreement from all mail >>> users. >> >> Indeed I know it's not the best, but this domain is collecting so many >> unwanted non-spam mails that it would really take >too much effort to get >> rid of them, and they're continuously increasing so I don't think that just >> removing the email >address from the website will do any better. >> I (well, they) just want that in their situation mailing lists are moved to >> the spam folder. >sounds more like nobody trains bayes or the wrong bayes >killing mailing-lists would also hit this list >what you want to do is just plain wrong Accurate spam detection should take into consideration the reputation of the sending mail server along with message content. Mailchimp, Constant Contact, and other major mass mailing companies are responsible senders that do a good job of preventing spam coming out of their mail servers. If they didn't, they would simply go out of business because all of us would block their messages. They have reliable unsubscribe links and processes so I let them through to the end user so they can unsubscribe to put the control back in the end user's hands. I block senders with invalid unsubscribe links/processes that just harvest/validate the email address. I agree with Reindl on this one, I would not try to block these legit senders. If you spend a little time training your bayes and whitelisting safe senders using SHORTCIRCUIT, your spam detection accuracy will become very reliable and you won't have to spend a lot of time playing whack-a-mole on new spam. It pays off in the end and lowers your SA scanning time. This works pretty well for me and should for most: shortcircuit USER_IN_WHITELIST on shortcircuit USER_IN_DEF_WHITELIST on shortcircuit USER_IN_BLACKLIST on shortcircuit USER_IN_DKIM_WHITELIST on shortcircuit USER_IN_DEF_DKIM_WL on shortcircuit USER_IN_SPF_WHITELIST on shortcircuit USER_IN_DEF_SPF_WL on shortcircuit RCVD_IN_MSPIKE_H5 on shortcircuit RCVD_IN_RP_CERTIFIED on shortcircuit RCVD_IN_RP_SAFE on shortcircuit RCVD_IN_DNSWL_HI on shortcircuit RCVD_IN_IADB_LISTED on I have built an extensive list of safe senders in the whitelist_from_* that will use the SHORTCIRCUIT (DKIM, SPF, RCVD) enabled above. P.S. Reindl usually comes across pretty harsh so don't take it personally.
