Shane wrote:
> As I stated in my original message, this server is a backup MX for several
> domains.
> So, postfix is configured with the following:
> relay_domains = hash:/etc/postfix/relay_table
> Where relay_table contains the list of domains that I will relay mail to.
> The problem is that amavis is quarantining these messages even though they
> aren't listed in @local_domains_maps.
> Shane
@local_domains_maps has nothing to do with whether a message will get
quarantined or not. You are accepting mail for your friend (an
additional domain). Your friend's mail will get processed by
amavisd-new. It may get quarantined. You can either stop accepting
mail for your friend's domain, set up Postfix to bypass amavisd-new if
it is addressed to someone in your friends domain, or set up
amavisd-new to bypass all checks (a policy bank could be used for this
purpose), or simply not quarantine messages addressed to your friend's
domain. Postfix works on the envelope recipient, so keep in mind what
might happen if the mail is addresses to both domains.
Here is one way to bypass checks (this was from a recent post). Let's assume
your domain is example.com.
@bypass_spam_checks_maps = ( [ "!.example.com", "." ] );
This says: don't bypass spam checks if the recipient's domain is
example.com, but bypass checks for any other domain.
Then you could supply the same rule to the other @bypass variables:
@bypass_banned_checks_maps = @bypass_header_checks_maps =
@bypass_spam_checks_maps;
This would still check for viruses (if you have configured virus
scanning). I would recommend you not quarantine viruses in this case.
(set $virus_quarantine_to = undef; to disable virus quarantine)
This is just one idea. Idea #2:
You could avoid quarantining spam for your friend by setting
$sa_kill_level_deflt to a very high level only for your friend's
domain:
$sa_kill_level_deflt = 9.0; # this is for domains other than your friend's
@spam_kill_level_maps = ( { '.friends.com' => 999.0 }, \$sa_kill_level_deflt, );
To avoid quarantining mail with bad headers, simply leave this default:
$final_bad_header_destiny = D_PASS;
Once again, set $virus_quarantine_to = undef; to disable virus quarantine.
So now we are left with banned files. For this, a policy bank could be
used. Here is how this could be set up:
In main.cf:
smtpd_recipient_restrictions =
permit_mynetworks,
reject_unauth_destination,
<...>
check_recipient_access hash:/etc/postfix/bypass_banned
The contents of the /etc/postfix/bypass_banned file could be:
[EMAIL PROTECTED] FILTER smtp-amavis:[127.0.0.1]:10026
[EMAIL PROTECTED] FILTER smtp-amavis:[127.0.0.1]:10026
[EMAIL PROTECTED] FILTER smtp-amavis:[127.0.0.1]:10026
<...>
(Don't forget to postmap the file)
In amavisd.conf, modify:
$inet_socket_port = [10024,10026];
and add:
$interface_policy{'10026'} = 'BYPASSBANNED';
$policy_bank{'BYPASSBANNED'} = {
bypass_banned_checks_maps => [1],
final_banned_destiny => D_PASS,
};
These are just ideas. Hopefully you have a better understanding of the
problem. I would not be surprised if Mark had some cool trick that
would make all this unnecessary.
Gary V
///
-------------------------------------------------------
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
[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/
