Vishy,
> Need help with getting disclaimer working with amavisd-new 2.6.4. I had
> configured disclaimer to work with 2.5.4 and recently upgraded amavisd to
> 2.6.4 and since then disclaimer stopped working.
>
> Following is my configuration related to disclaimer in amavisd.conf
>
> $altermime = '/usr/bin/altermime'; # a path to the program
> @altermime_args_disclaimer = qw(--verbose
> --disclaimer=/etc/amavisd/disclaimer.txt
> --disclaimer-html=/etc/amavisd/disclaimer.html);
> $defang_maps_by_ccat{+CC_CATCHALL} = [ 'disclaimer' ];
> $policy_bank{'MYUSERS'} = {
> originating => 1,
> allow_disclaimers => 1,
> };
>
> The setup has postfix+amavisd-new+cyrus-imap. As mentioned earlier this
> configuration was working with amavisd 2.5.4 but has stopped working with
> 2.6.x. The only time it works is when a user send mail using webmail
> (also configured on the same server as postfix+amavis). For mail sent
> using any other clients like Outlook, Thunderbird etc., disclaimer is no
> longer working.
>
> Could someone help me get disclaimer working with 2.6.x
Sorry for a long delay. I finally tried your setup, and it does work here.
One difference between 2.5.4 and 2.6.4 is:
amavisd-new-2.6.0 release notes:
- an additional requirement for loading a policy bank 'MYUSERS' is that
'originating' flag must be on, which typically means that mail must
be coming from internal networks or from authenticated roaming users
to be able to load a policy bank 'MYUSERS';
so I suspect that what the $originating flag is not being turned on
for mail from your SMTP MUA clients, yet it is being turned on by
mail from your webmail server.
The $originating flag is either turned on implicitly by a client's IP
address matching @mynetworks, or explicitly through a policy bank
typically attached to a dedicated TCP port number, to which MTA
will feed mail from internal or authenticated roaming clients.
A debug log would tell if my guess is right.
Mark
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
