Stefan,
> following amavisd-new's documentation on enabling DKIM signing, I've
> created a policy bank for Mailman mailing list traffic:
>
> $policy_bank{'POSTQ-MAILMAN'} = {
> originating => 1,
> forward_method => 'smtp:127.0.0.1:10027',
> smtpd_discard_ehlo_keywords => ['8BITMIME'],
> mynetworks_maps => [],
> ...
> }
>
> If I connect to the TCP port providing this policy bank and issue a
> "XFORWARD" command, amavisd-new loads the MYNETS policy bank on top of
> the one I defined.
>
> Is this intended behaviour or a bug, perhaps lef over from introducing
> @client_ipaddr_policy? Or perhaps, I'm doing it wrong :-P
Sahil Tandon wrote:
> I am not sure about your problem, but according to RELEASE_NOTES,
> @client_ipaddr_policy needs to be explicitly re-defined if you modify
> @mynetworks_maps in amavisd.conf.
Indeed, it is an unfortunate consequence of how @client_ipaddr_policy
was introduced. This list is now the only source of mappings of an IP
address to a policy bank name. The @mynetworks_maps only serves
to populate the initial/default value of @client_ipaddr_policy
and is later ignored.
Try:
$policy_bank{'POSTQ-MAILMAN'} = {
originating => 1,
forward_method => 'smtp:127.0.0.1:10027',
smtpd_discard_ehlo_keywords => ['8BITMIME'],
client_ipaddr_policy => [],
...
}
Mark
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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/
