David B Funk <[EMAIL PROTECTED]> wrote: > On Mon, 1 Mar 2004, Bob George wrote: > [...] >> So am I correct in thinking any spams to any >> un/poorly-moderated lists from domains listed in the default >> whitelist probably will sail through with a high (negative) >> spam score, right? > > That's the net result of whitlisting a list. ANY post (legit > or spam) that makes it thru the listserver gets "blessed". > Now note that the "def_whitelist.." stuff only gives a -15 > score, not the full bore -100 so the damage shouldn't be > -too- severe.
Ah, I'd missed the -15, so THAT'S not too bad. I'll re-read the whitelist docs again. If AWL is in use, a first-time spammer that manages to post via one of the whitelisted listservers also gets an entry in a user's local AWL with a starting score reduced by 15, no? And that spammer's domain probably has nothing to do with that listed in the whitelist_to_rcvd entry, no? What bit me, I believe, was the fact that AWL entries remain in play even AFTER white/blacklists are updated. An entry in a system config rippled changes down to user AWLs that were persistent after the system config was fixed. In my case, only the spamd user was affected, but I could see a simple configuration goof rippling to hundreds of users' AWLs. Thanks for the clarification! - Bob
