R.Smits wrote:
>>
>>> This is what I know,
>>> ----------------------------
>>> mynetworks = 127.0.0.0/8 !192.168.1.1 192.168.1.0/24
>>
>>> In amavisd.conf @mynetworks determines which clients will use the
>>> 'MYNETS' policy bank:
>>
>>> @mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
>>> !192.168.1.1 192.168.1.0/24 );
>>
>>> And you would configure the 'MYNETS' policy bank as desired:
>>
>>> $policy_bank{'MYNETS'} = { # clients in @mynetworks
>>> bypass_spam_checks_maps => [1], # don't spam-check internal mail
>>> };
>>> ----------------------------
>>> This should work, but the mail coming from local (mynetworks) is now not
>>> being scanned when going to the outside world. This we DO want. We are
>>> hosting multiple domains, so we must check on IP number, not domain name.
>>> Your solution will make everyone from yourdomain.com a spam_lover ? Or
>>> am I wrong ?
>>
>>> Greetings... Richard
>>
>> 1 = true
>> 0 = false
>>
>> bypass_spam_checks_maps => [1], # true for all recipients
>>
>> bypass_spam_checks_maps => [
>> {'mydomain.example.com' => 1, # True for our domain
>> '.' => 0, # false for everyone else
>> }
>> ],
>>
>> I believe this would work as well (in other words, true is assumed if
>> the domain is listed, and false is assumed if it is not):
>>
>> bypass_spam_checks_maps => [[qw( .example.com .example.net )]],
>> # domains we host
>>
>> You could use spam_lovers_maps instead of bypass_spam_checks_maps
>> as Mark has shown. I think bypassing would save processing on
>> internal mail, but on the other hand, scanning may give Bayes some
>> needed ham.
>>
>> Gary V
> I'm sorry, but I am a bit confused,
> Lets start again :-)
> We want to whitelist everything from our network. We can do this with
> the policy bank MYNETS. (No problem here)
> But now comes the big issue, we do NOT want to whitelist to the outside
> world. (Outside our networks)
This part works, right? Spam that scores over kill_level should not
get delivered to domains not listed in the policy bank.
> We want to sent that mail back to the senders internally. DSN
Actually, the mail is not returned to the sender per se. A DSN
can be generated, but this may require changing $final_spam_destiny.
> I believe the above examples do not solve this, or am I wrong ?
Half and half depending on current $final_spam_destiny.
You can change the $final_spam_destiny in the policy bank
so it generates DSN:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
bypass_spam_checks_maps => [[qw( .example.com .example.net )]],
final_spam_destiny => D_BOUNCE,
};
This will allow clients included in @mynetworks to bypass spam checks
for mail sent to the listed domains (only). Any mail found to be spam
(which can only happen for domains other than the listed ones) should
get bounced (DSN created by amavisd-new and mailed to sender).
As an alternate:
$policy_bank{'MYNETS'} = { # clients in @mynetworks
spam_lovers_maps => [[qw( .example.com .example.net )]],
final_spam_destiny => D_BOUNCE,
};
This should generate a DSN for all spam sent from @mynetworks,
but still deliver a copy of the original message to the listed
domains. I have not tested, so give it a try.
Gary V
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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/
