Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have setup amavis as follows:

$policy_bank{'ORIGINATING'} = {  # mail originating from our users
  originating => 1, # indicates our client, introduced in amavisd-new-2.5.0
  spam_admin_maps  => ["spamalert\@$mydomain"],  # warn of spam from us

@spam_lovers_maps = ([ qw( abuse@ )]);

I have added spamcop to spam_lovers, because I send/forward spam there myself, and Amavis was blocking it before.

Now, I've got an "SPAM FROM LOCAL" warning to the spam_admin address, after having sent a bunch of spam to the spamcop submit address (using my gmail account as a sender, not the local domain - but sent through my smtp).

I do not want to get the warnings when spam is sent from LOCAL to any spam lovers.

share|improve this question
up vote 2 down vote accepted

@spam_admin_map uses also a hash lookup table and lookup is done with a per-recipient key.

Therefore you can replace the spam_admin_maps line in the policy bank with something like this:

spam_admin_maps => [ {"abuse\" => undef},  "spamalert\" ],

Examples can be found in the file amavisd.conf-sample which is delivered with amavis.

share|improve this answer
Thanks for your answer! I am currently using the following as a workaround: @bypass_spam_checks_maps = ([ qw( ) ]); and @bypass_virus_checks_maps = ([ qw( ) ]); – blueyed Apr 13 '11 at 15:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.