Re: best way to whitelist this list?
A. Schulze wrote: > Hello, > > today I was notified by ezmlm that my MTA rejected messages to me. > Messages to this list where classified as spam by .. spamassassin. > OK, no surprise some messages look spammy. > > As usual: there is one solution that is smart, fast and obvious. But > sometimes this one is also wrong. > So I ask the list: (how) do you whitelist this list? Personally, I'm fond of whitelisting most of the mailing lists I'm on by telling the glue layer to not pass the message to SA in the first place. I call SA from procmail on message delivery, so a procmail recipe like so: :0 * ^List-Id: $DEFAULT/.spam-stomping/ placed ahead of the segment that passes the message to SA, files all messages with the appropriate List-Id header in the folder I put several spam-related lists in without passing them to SA at all. For my purposes I haven't decided if one side effect is really good or bad; personal CCs or direct replies go to my Inbox instead of the designated list folder. -kgd
Re: best way to whitelist this list?
Am 21.09.2015 um 18:56 schrieb Kris Deugau: A. Schulze wrote: today I was notified by ezmlm that my MTA rejected messages to me. Messages to this list where classified as spam by .. spamassassin. OK, no surprise some messages look spammy. As usual: there is one solution that is smart, fast and obvious. But sometimes this one is also wrong. So I ask the list: (how) do you whitelist this list? Personally, I'm fond of whitelisting most of the mailing lists I'm on by telling the glue layer to not pass the message to SA in the first place. I call SA from procmail on message delivery, so a procmail recipe like so: :0 * ^List-Id: $DEFAULT/.spam-stomping/ placed ahead of the segment that passes the message to SA well, that is *easy* to forge as any header whitelist_auth is based on SPF/DKIM and combined with SHORTCIRCUIT prodcues zero load signature.asc Description: OpenPGP digital signature
Re: best way to whitelist this list?
Am 20.09.2015 um 05:10 schrieb Reindl Harald: Am 19.09.2015 um 20:12 schrieb A. Schulze: So I ask the list: (how) do you whitelist this list? whitelist_auth *@spamassassin.apache.org works. it trigger USER_IN_SPF_WHITELIST=-100 thanks! Andreas
Re: best way to whitelist this list?
On 2015-09-19 20:12 +0200, A. Schulze wrote: > today I was notified by ezmlm that my MTA rejected messages to > me. Messages to this list where classified as spam by .. spamassassin. All of today's messages here scored around -7.5 for me, with no special handling. -- Please *no* private copies of mailing list or newsgroup messages. Rule 420: All persons more than eight miles high to leave the court.
Re: best way to whitelist this list?
Am 19.09.2015 um 20:12 schrieb A. Schulze: today I was notified by ezmlm that my MTA rejected messages to me. Messages to this list where classified as spam by .. spamassassin. OK, no surprise some messages look spammy. As usual: there is one solution that is smart, fast and obvious. But sometimes this one is also wrong. So I ask the list: (how) do you whitelist this list? whitelist_auth *@spamassassin.apache.org signature.asc Description: OpenPGP digital signature
best way to whitelist this list?
Hello, today I was notified by ezmlm that my MTA rejected messages to me. Messages to this list where classified as spam by .. spamassassin. OK, no surprise some messages look spammy. As usual: there is one solution that is smart, fast and obvious. But sometimes this one is also wrong. So I ask the list: (how) do you whitelist this list? Thanks, Andreas
Re: best way to whitelist this list?
A. Schulze skrev den 2015-09-19 20:12: So I ask the list: (how) do you whitelist this list? X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 seem to me its not needed :=) but sat whitelist_from_dkim your own dkim signature if needed do more lines of that if more is needed, eg dkim signed, but content is spamming, the, most importange part possible is to eg disable autolearn, with imho happens if std rules are in use missing that point will learn spam as ham in bayes why is this maillist here missing spf helo pass ?, hmm
Re: best way to whitelist this list?
On 19 Sep 2015, at 14:12, A. Schulze wrote: Hello, today I was notified by ezmlm that my MTA rejected messages to me. Messages to this list where classified as spam by .. spamassassin. OK, no surprise some messages look spammy. As usual: there is one solution that is smart, fast and obvious. But sometimes this one is also wrong. So I ask the list: (how) do you whitelist this list? A layered defense in depth requires matching layered whitelisting... All of my list-sub addresses (which match a pattern) are exempted from some relatively error-prone (~0.01% FP) tactics ahead of content filtering and all content filtering except SA. Inside SA, I use whitelist_to to further exempt the target. However: I have USER_IN_WHITELIST_TO reduced to -3 because these addresses are *more* exposed than a normal address and shouldn't get the standard -6. To further protect actual list mail (in contrast with off-list replies and spam from harvesters,) I use whitelist_from_spf where possible (including all apache.org lists,) falling back to whitelist_from_rcvd for other lists. The few lists I've subscribed to over the years where neither of those have been usable have all shut down anyway.
