From Gary:
> ...If the mail is addressed to
> multiple recipients, and one of the recipients disagrees that
> the scan should be bypassed, the scan will still take place.
...or with cached spam-check results if a same-body
mail was recently checked, perhaps for different recipients.
Shane, incre
Shane wrote:
> Gary V <[EMAIL PROTECTED]> [2005-09-29 10:59]:
>> This worked:
>> @spam_quarantine_to_maps = (
>> { '.example.com' => '', # turn off quarantine for this recip
>> },
>> $spam_quarantine_to, # for everybody else use a global default
>> );
> I must be doing something crazy. I
Gary V <[EMAIL PROTECTED]> [2005-09-29 10:59]:
> This worked:
> @spam_quarantine_to_maps = (
> { '.example.com' => '', # turn off quarantine for this recip
> },
> $spam_quarantine_to, # for everybody else use a global default
> );
I must be doing something crazy. I have some domains that I
Gary,
> Mark, this failed for me:
> $spam_quarantine_to = '[EMAIL PROTECTED]';
> @spam_quarantine_to_maps = (
> { '.example.com' => undef, # turn off quarantine for this recip
> },
> $spam_quarantine_to, # for everybody else use a global default
> );
> This worked:
> @spam_quarantine_to_ma
Mark wrote:
> 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 amavisnew
As a backup MX server for your friend, since spammers target the
secondary MX, 99% of the mail addressed to your friend's domain
will probably be spam. So, you will not be doing your friend any
favors by bypassing spam checks for him/her. Another alternative
is to discard mail quarantined to their
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 talkin
Gary V <[EMAIL PROTECTED]> [2005-09-28 20:58]:
> This can be simplified by using a regexp map.
>
> check_recipient_access regexp:/etc/postfix/bypass_banned
>
> The contents of the /etc/postfix/bypass_banned file could be:
> /^(.*)@friends\.com$/ FILTER smtp-amavis:[127.0.0.1]:10026
Thanks a
Gary wrote:
> 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.
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 tha
Tony Earnshaw <[EMAIL PROTECTED]> [2005-09-29 00:37]:
> Whatever, this isn't an Amavis question, but a Postfix question. Mail
> for non-existent users on your host or in your domain should never be
> accepted by your Postfix server, wherever the mail comes from, unless
> those users are explicit
Shane Hickey wrote:
I'm _very_ new to amavis, so I apologize if these are foolish
questions. I attempted to find the answers on my own, but I wasn't having much
luck.
Here's the deal. I'm running amavisd-new-2.3.3 installed from Gentoo's
portage tree. My MTA is Postfix-2.1.
It never fails, work up the nerve to post your question to a mailing-list and
in second you'll find the answer on your own. That is, I found a partial
answer, at least.
Apparently amavisnewsql-0.8.0-1.4 fixes the symptoms of this problem. If a
message in the quarantine has a BSMTP RCPT TO: th
Howdy all,
I'm _very_ new to amavis, so I apologize if these are foolish
questions. I attempted to find the answers on my own, but I wasn't having much
luck.
Here's the deal. I'm running amavisd-new-2.3.3 installed from Gentoo's
portage tree. My MTA is Postfix-2.1.5-r2 (also f
14 matches
Mail list logo