whitelist sender when amavisd-new-20030616-p10 to amavisd-new-2.3.3

I'm upgrading a server from amavisd-new-20030616-p10 to
amavisd-new-2.3.3. The old version had the following line in
the
amavisd.conf file:

	read_hash(\%whitelist_sender,
'/etc/amavis/whitelist_sender');

/etc/amavis/whitelist_sender is of the form:

userexample.com
.example2.com
example3.com

Although I realise that the later version of amavis has much
more
flexible control over whitelisting, and I also realise the
shortcomings
of whitelisting by sender address, I really want to
replicate the same
whitelist under the new version of amavis, at least to start
with. I've
tried the following in /etc/amavis/conf.d/50-user:

bypass_spam_checks_maps =
(read_hash("/etc/amavis/whitelist_sender") );

...but it still marks spam sent from an address listed
whitelist_sender.
I'm missing something obvious: can someone point me in the
right direction?

Thanks.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Keith wrote:

> I'm upgrading a server from amavisd-new-20030616-p10
to
> amavisd-new-2.3.3. The old version had the following
line in the
> amavisd.conf file:

>         read_hash(\%whitelist_sender,
'/etc/amavis/whitelist_sender');

> /etc/amavis/whitelist_sender is of the form:

> userexample.com
> .example2.com
> example3.com

> Although I realise that the later version of amavis has
much more
> flexible control over whitelisting, and I also realise
the shortcomings
> of whitelisting by sender address, I really want to
replicate the same
> whitelist under the new version of amavis, at least to
start with. I've
> tried the following in /etc/amavis/conf.d/50-user:

> bypass_spam_checks_maps =
(read_hash("/etc/amavis/whitelist_sender") );

> ...but it still marks spam sent from an address listed
whitelist_sender.
> I'm missing something obvious: can someone point me in
the right direction?

The obvious part is bypassing is done for recipients, not
senders.

One option, in 20-debian_defaults - in score_sender_maps, look for:

# 
read_hash("/var/amavis/sender_scores_sitewide"),

You could uncomment and configure this. Copy your existing
file over, and
assign a score to each sender. You can give a negative
(whitelist-ish) score,
or positive (blacklist-ish) score:

userexample.com -3
.example2.com -7.5
example3.com -5.0
badguy.com 5

Make sure you give each sender a score.

You could copy the entire score_sender_maps section
from
20-debian_defaults to 50-user if you prefer to leave
20-debian_defaults untouched.

Gary V


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Keith wrote:

> I'm upgrading a server from amavisd-new-20030616-p10
to
> amavisd-new-2.3.3. The old version had the following
line in the
> amavisd.conf file:

>         read_hash(\%whitelist_sender,
'/etc/amavis/whitelist_sender');

> /etc/amavis/whitelist_sender is of the form:

> userexample.com
> .example2.com
> example3.com

> Although I realise that the later version of amavis has
much more
> flexible control over whitelisting, and I also realise
the shortcomings
> of whitelisting by sender address, I really want to
replicate the same
> whitelist under the new version of amavis, at least to
start with.

Just so you know, there is nothing preventing you from using
your
existing setting for hard whitelisting, but you could
modernize it a bit:

whitelist_sender_maps =
read_hash('/etc/amavis/whitelist_sender');

Gary V


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/