I know there are varying opinions on whether the AutoWhiteList option is a good idea or not, and I'm starting to have my doubts, but bare with me as I attempt to describe problems I am having even maintaining it at what I would consider an acceptable level as an administrator.
Firstly, I'm using spamassassin-3.0.2-1, if it matters. Generally, I am pleased with the AWL feature, but as an administrator, better and more functional tools for maintaining it are really necessary (and I hope I'm missing something and someone here can lend advice, if so). Firstly, documentation describes two ways to adjust things in the autowhitelist for your installation (and the documentation is really poor, at best). The problem comes with how these adjustments are implemented. Let me give an example of an email that is firing your AWL and adjusting scores below a spam threshold because of it. If this adjustment is radical, when I go through my logs to tweak the AWL, I would like to be able to adjust it, but you simply cannot under the current implementation, unless I am missing something. I'm not even going to get into some of the features missing in using 'spamassassin -R' on an email, but removing every instance of every single email address from whatever email you pass to it is ludicrous. It removes senders, receivers; it removes everything in the entire email that even looks like an email address. It doesn't even care that the initial placement of the sender in the AWL list actually looked at the email to determine what it was.. it just removes every single email address in that email from the AWL list. Why doesn't it use the same logic it used to add or compare that sender to the AWL list when you do a removal with -R? The concept that it doesn't is really ludicrous. The second thing it does that is improper is that the AWL list is NOT just based on an 'email address', it is based on an email address TIED to a #.# IP range. Where is the argument that allows one to specify this IP? Am I missing it? The -R argument, as I have experienced it, removes EVERY SINGLE instance of that email-address "FROM" sender, without regard to the FACT that that address could have numerous IP pairs associated with it. So, without further complaining, someone please point me in the right direction with regard to how to make intelligent adjustments to the AWL. I have written scripts which parse out the proper email addresses and IPs, but I can only pass an 'email address' to the removal portion of spamassassin, and as I have stated, that removes every single instance of that email address, regardless of whether or not it has 1 or 100 entries in the AWL with different IP blocks associated to it. (And, by the way, if anyone else is writing scripts to pass to spamassassin to adjust the AWL intelligently and for their specific installations, I can give alot of advice on what is just plain 'odd' behaviour from spamassassin when it parses an email message after being passed the '-R' argument. Many of them are certainly bugs, but I can get around them if someone can explain how I can inform spamassassin to delete a specific emailaddress+IP pair instead of every single emailaddress it matches). Alternatively, the options which allow a "+100" adjustment to the AWL for a specific email address, I have not played with much, but I would think the same question/problem would arise. What IP, in the #.# format the autowhitelist uses, does that refer to, or does it just add 100 to them all? Thanks for any help, -- View this message in context: http://www.nabble.com/AWL-maintenance-t1304878.html#a3476947 Sent from the SpamAssassin - Users forum at Nabble.com.
