Joel,
> Ok, I will adjust my configuration. But according to the new-docs,
> checks may be performed (forced) when there are multiple recipients and
> one recipient has checks and the other doesn't. In this case I'm
> sending to one recipient, who has BypassBannedChecks=TRUE set in LDAP.
> Why is the check still being performed?
Because I ran out of time preparing the 2.3.2 release to optimize
that code path. It still plays according to the docs, except somewhat
surprisingly.
> And why does don't I see the
> lookup_ldap_attr(amavisbypassbannedchecks)?
Because your bypass_banned_checks_maps lookup resulted in unconditional
true (due to having bypass_banned_checks_maps=>[1] in your policy bank
MYNETS if I remember right) the LDAP lookup was not done.
Later on, because you have $banned_namepath_re nonempty, it overruled
the earlier decision:
my($bnpre) = cr('banned_namepath_re');
if (!$any_table_in_recip_tables && !(ref $bnpre && ref $$bnpre)) {
do_log(3,"skipping banned check: no applicable lookup tables");
} else {
do_log(4,"starting banned checks - traversing message structure tree");
due to the fact that when using the $banned_namepath_re the
optimization was not done as it could have been. Not nice, but not incorrect.
Mark
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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/
