> > Can be done through a custom hook, e.g.:
> Not sure, if I can use it (because I don't understand perl :-) )
/etc/etc-custom.conf :
package Amavis::Custom;
use strict;
sub new {
my($class,$conn,$msginfo) = @_;
bless {}, $class;
}
sub before_send {
my($self,$conn,$msginfo) = @_;
if ($msginfo->originating) { # ...add other conditions if necessary
# errata: http://www.rfc-editor.org/errata_search.php?rfc=5518
my($hdr_edits) = $msginfo->header_edits;
$hdr_edits->add_header('VBR-Info',
'md=example.com; mc=all; mv=dwl.spamhaus.org;');
}
};
1; # insure a defined return
/etc/amavisd.conf :
...
include_config_files('/etc/amavisd-custom.conf');
...
> > Indeed, or easier through $forward_method:
> >
> > $policy_bank{'ORIGINATING'} = {
> > ...
> > forward_method => 'smtp:[127.0.0.1]:10025',
> > ...
> > };
>
> 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' ],
...
};
Mark
------------------------------------------------------------------------------
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
