Just wanted to add that this particular line is incorrect: meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST|| USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO|| USER_IN_BLACKLIST)
That will have Blacklisted email filters classified as ham. - Julian On Sun, Feb 24, 2008 at 8:07 AM, Micah Anderson <mi...@riseup.net> wrote: > On Sun, 24 Feb 2008 02:15:24 +0100, Matthias Leisi wrote: > > > Micah Anderson schrieb: > > > > | [surprisingly low scores] > > | The spams can be pulled from here: http://micah.riseup.net/spams > > > > Most (all?) of the samples are forwarded through some debian.org > > mechanism. In order for blacklists to take full effect, you should > > configure your trust path (trusted_networks etc) accordingly. > > My trusted_networks is set to: > > trusted_networks 202.12.162. > trusted_networks 10.0. > trusted_networks 10.8.0. > > The first is trusting everything in that IP space, which we control, the > second is a private network, and the third is a private network. Am I > specifying those incorrectly perhaps? > > I'm also short-circuiting on trusted-relay chained messages, using the > following: > > meta SC_HAM (USER_IN_WHITELIST||USER_IN_DEF_WHITELIST|| > USER_IN_ALL_SPAM_TO||NO_RELAYS||ALL_TRUSTED||USER_IN_BLACKLIST_TO|| > USER_IN_BLACKLIST) > priority SC_HAM -1000 > shortcircuit SC_HAM ham > score SC_HAM -20 > > But I log in the headers all short-circuit status, with the following > (and you wont see short-circuiting in the examples i posted): > > status > add_header all Status "_YESNO_, score=_SCORE_ required=_REQD_ > tests=_TESTS_ shortcircuit=_SCTYPE_ autolearn=_AUTOLEARN_ > version=_VERSION_" > > Do I have something misconfigured in my trust path? I do have a forward > from a debian.org email address that occasionally sends me legit email > (although it does seem like a lot of spam gets through there), but I dont > believe I have that domain in a whitelist anywhere. > > thanks > micah > >
