up vote 5 down vote favorite
share [g+] share [fb]

I'd like to know how to configure amavisd-new to only scan for Spam on particular clients (IPs, CIDRs or hostnames) or alternatively sender's email domain.

I know that it is possible to do it on a recipient's mail address but not on how to do it for the sender's mail address. It is even possible to do it on a recipient's IP address with policy banks. But my approach should be to be independent of recipient and only relay on the sender.

What I want to accomplish is to only scan mails originating from Yahoo, Google, Hotmail and the other big senders. So it is easier to configure which senders should be observed than the ones that shouldn't.

I known that it is easier to achieve on the MTA side, but that is not part of the question because I already go a solution on the MTA side. I want to do it on amavisd-new. And it doesn't help to know how to put senders on a whitelist, as this still means that the mail goes through all the scanning but then gets a high negative score. The mail shouldn't be scanned at all unless sent by the big players.

So which parameters in amavisd-new is the right one to enable scanning for particular senders and only for these?

link|improve this question
Have you seen these examples? If so, what's wrong with them? – syneticon-dj Jan 14 at 21:15
@syneticon-dj I know them. This is the solution I already have (fourth paragraph above). But they are after queue filters and I need amavis to run as a before queue filter and then this does not work. And this is to bypass particular senders; I want the opposite to only scan particular senders and bypass the rest. – mailq Jan 14 at 21:18
I can't see why it would not work before-queue. And reversing the logic to scan only particular senders and not scan anything else is just reversing the configuration settings for your policy banks - set up bypass_*_checks_maps variables as your default config and make sure the maps are empty for your yahoo.com policy bank. – syneticon-dj Jan 14 at 21:27
Why wouldn't whitelisting work for not calling SpamAssassin? From amavisd.conf-sample: "If ALL recipients of the message either white- or blacklist the sender, spam scanning (calling the SpamAssassin) is bypassed, saving on time." "ALL" recipients should be affected when using @whitelist_sender_maps shouldn't it? – sebbow Apr 5 at 11:56
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.