Re: [AMaViS-user] Multiple recipients and bypass_spam_checks_maps

Mark Martinec wrote:
> Chris,
>
>
>>- It would be nice if $at_with_user could be configured in the config
>>file instead of the binary.
>
>
> I'll consider it. You are probably interested in having this configurable
> for LDAP lookups, not necessarily for hash and SQL lookups.
Correct. We've stored wildcardaccounts as @domain.com. I don't know if
this is only nessesary for LDAP. I guess it's more related to the way
mailaddressess are stored.

>>- If there are multiple recipients of which some have spamchecks enabled
>>and some don't, the variable $bypass_spam_checks_maps is not correctly
>>treated for the recipients that have bypass_spam_checks set to 'TRUE'.
>>They are treated as if they would have set bypass_spam_checks set to
>>'FALSE'. I can send the complete logging if needed (56k), here's a snip
>>of it:
<snip>
>
>
> It looks normal. You probably assumed that bypass* also implies *lover,
> which it does not. If the mail got checked for one reason or another (e.g.
> in multirecipient cases), despite recipient not explicitly requesting it
> (bypass=true), the check result still affects the outcome.
> When setting bypass* to true for some recipient, you should in almost
> all cases also want to set *lover to true for this recipient.
>
> See first two sections in:
> http://www.ijs.si/software/amavisd/a...-new-docs.html
That cleared things up. Thanks!

Chris


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/