> I did a diff to check out the difference between Debian and vanilla Amavis
> 2.6.1 and it looks like it is about the Debian way of reading the config
> files. The patch looks like it worked. See the patched Debian amavisd-new
> snippet:
>
> 9720 my($bypassed_b) = lookup(0,$recip,
> @{ca('bypass_banned_checks_maps')});
> 9721 $r->bypass_banned_checks($bypassed_b);
> 9722 }
> 9723 if (!$r->bypass_spam_checks) {
> 9724 my($bypassed_s) = lookup(0,$recip,
> @{ca('bypass_spam_checks_maps')});
> 9725 $r->bypass_spam_checks($bypassed_s);
> 9726 }
> 9727 }
> 9728
> 9729 # Check if we need to do last minute policy changes
> 9730 if (ref $custom_object) {
> 9731 $which_section = "custom-process_policy";
> 9732 eval {
> 9733 my $new_policy_bank = $custom_object->process_policy($conn,
> $msginfo,\%current_policy_bank); 1;
> 9734 %current_policy_bank = %{ $new_policy_bank };
> 9735 } or do {
>
> Compare the the patch file:
>
> 16 @@ -9705,6 +9706,20 @@
> 17 $r->bypass_spam_checks($bypassed_s);
> 18 }
> 19 }
> 20 +
> 21 + # Check if we need to do last minute policy changes
> 22 + if (ref $custom_object) {
> 23 + $which_section = "custom-process_policy";
> 24 + eval {
>
>
Only vanilla Amavisd-new is supported. You can try use another modified
version, but I'm not going to entertain any bug reports.
-N
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
