amavis wrote:

 

>> -----Original Message-----
>> I have my whitelist file setup in /var/amavis/whitelist_sender
>> 
>> In /etc/amavisd.conf I have the following line :
>> 
>> read_hash("/var/amavis/whitelist_sender"),
>> 
>> 
>> When I receive an email from address of [EMAIL PROTECTED] - it 
>> seems to match the whitelist, yet still spam scans, and takes 
>> actions based on the scan.. so it doesn't seem to be 
>> listening to the whitelist ...  here is a copy from my log 
>> file in log level 5
>> 
>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10)
>> lookup_hash([EMAIL PROTECTED]) matches key "[EMAIL PROTECTED]", result=1 
>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) lookup
>> (score_sender<[EMAIL PROTECTED]>) => true,  "[EMAIL PROTECTED]" matches, 
>> result="1", matching_key="[EMAIL PROTECTED]"
>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) wbl: 
>> soft-blacklisted (1) sender <[EMAIL PROTECTED]> => <[EMAIL PROTECTED]>, 
>> recip_key="."
>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) 
>> spam_scan: 
>> DSPAM not available, skipping it
>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) 
>> calling SA parse, SA version 3.0.4 Jul 24 09:38:07 ns1 
>> /usr/local/sbin/amavisd[3314]: (03314-10) CALLING SA check 
>> Jul 24 09:38:09 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) 
>> RETURNED FROM SA check, time left: 0 s Jul 24 09:38:09 ns1 
>> /usr/local/sbin/amavisd[3314]: (03314-10) prolong_timer after 
>> spam_scan_SA: remaining time = 480 s Jul 24 09:38:09 ns1 
>> /usr/local/sbin/amavisd[3314]: (03314-10) spam_scan: 
>> hits=6.346 tests=[AWL=-0.560,BAYES_50=0.001,HTML_80_90=0.1
>> 46,HTML_IMAGE_ONLY_20=0.446,HTML_MESSAGE=2,HTML_TITLE_EMPTY=0.
>> 004,MIME_HTML_ONLY=3,NO_REAL_NAME=0.007,UNDISC_RECIPS=1.302]
>> 

> If I'm understanding correctly, your whitelist is per-recipient.  The
> message would need to be scanned for the base SA score to allow other
> recipients to provide their own score boosts.  Look at the log entries that
> follow the one above to see how the message was treated for each given
> recipient.

> -Mike

Show an example of the contents of whitelist_sender. It appears to me
that you have no score after the sender's email address:

[EMAIL PROTECTED]
[EMAIL PROTECTED]

and the lookup is expecting to find a key/value pair, like this:

[EMAIL PROTECTED] -3.0
[EMAIL PROTECTED] -6.0

It does not find the 'value' part of the key/value pair, so it returns
"1", which read_hash is programmed to do. Adding "1" to the score
blacklists the sender, and possibly results in:

>> Jul 24 09:38:07 ns1 /usr/local/sbin/amavisd[3314]: (03314-10) wbl:
>> soft-blacklisted (1) sender <[EMAIL PROTECTED]> => <[EMAIL PROTECTED]>, 
>> recip_key="."

I could be wrong.
Where is this read_hash statement located? Is it inside @score_sender_maps(); ?

If you want to do a hard whitelist, I think you would use:
read_hash(\%whitelist_sender, '/var/amavis/whitelist_sender');

This statement would not go inside @score_sender_maps(); and would not
require a score for each sender. I have not tested this stuff, but I
think this is how it works.

Gary V



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to