Shane,
Besides options Gary gave, you can just plainly disable quaranatine
for recipients or domains for which you do not want to keep quarantine
(no need to change kill level or turn off checking if you do not want to).
I believe this is also what the Q&A entry in amavisnewsql you found
is talking about.
@spam_quarantine_to_maps = (
{ '.relayed-domain1.com' => undef, # turn off quarantine for this recip
'.relayed-domain2.com' => undef,
'[EMAIL PROTECTED] => undef,
'.' => $spam_quarantine_to, # for everybody else use a global default
}
);
or equivalently (a matter of taste):
@spam_quarantine_to_maps = (
{ '.relayed-domain1.com' => undef, # turn off quarantine for this recip
'.relayed-domain2.com' => undef,
'[EMAIL PROTECTED] => undef,
},
$spam_quarantine_to, # for everybody else use a global default
);
The same can be achieved with SQL lookups, just use field
policy.spam_quarantine_to and set it to an empty string
for those recipients or domains for which you want
to turn off quarantining, and keep the field at NULL
for remaining recipients to cause a fallback to a static
global default which is the value of $spam_quarantine_to.
See also
http://www.ijs.si/software/amavisd/amavisd-new-docs.html#quarantine
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
