:-)
>>
>> I tred that one out, but it does not use the correct forward_method:
>
> Sorry, I gave bad advise, the forward_method is somewhat special
> since the invention of multiple-backends failover mechanism.
> Just use the forward_method_maps, as you suggested:
>
> $policy_bank{'ORIGINATING'} = {
> ...
> forward_method_maps => [ 'smtp:[::1]:10125' ],
> ...
> };
Sorry, but that does not work either (that would fix header_checks-usage in
postfix, so important) ;-) It always uses the global defined forward_method.
$forward_method = 'smtp:[::1]:10025';
$notify_method = $forward_method;
$policy_bank{'ORIGINATING'} = {
forward_method_maps => [ 'smtp:[::1]:10125' ],
};
$policy_bank{'MYNETS'} = {
originating => 1,
warnbadhsender => 1,
bypass_banned_checks_maps => [1],
terminate_dsn_on_notify_success => 0,
final_virus_destiny => D_DISCARD,
final_spam_destiny => D_DISCARD,
spam_admin_maps => [ $RNSPOSTMASTER ],
os_fingerprint_method => undef,
};
$policy_bank{'MYUSERS'} = {
originating => 1,
allow_disclaimers => 1,
final_virus_destiny => D_BOUNCE,
final_spam_destiny => D_BOUNCE,
spam_admin_maps => [ $RNSPOSTMASTER ],
os_fingerprint_method => undef,
};
$policy_bank{'MAILMAN'} = {
originating => 1,
bypass_virus_checks_maps => [1],
bypass_spam_checks_maps => [1],
bypass_banned_checks_maps => [1],
os_fingerprint_method => undef,
};
$policy_bank{'TRUSTED'} = {
bypass_spam_checks_maps => [1],
bypass_banned_checks_maps => [1],
};
Christian
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
Please visit http://www.ijs.si/software/amavisd/ regularly
For administrativa requests please send email to rainer at openantivirus dot
org
