Alan,
> With the new penpals feature in 2.4.2, I thought it might be time
> to turn on sql logging and pass my outgoing mail through
> amavisd-new (previously, I was only passing incoming mail).
>
> But I'd like to bypass virus and spamchecking for outgoing
> mail and I can't seem to make that work. Perhaps someone sees
> an obvious screwup?
>
> @mynetworks = qw( 127.0.0.0/8 [::1] [FE80::]/10 [FEC0::]/10
> 10.0.0.0/8 );
> $policy_bank{'MYNETS'} = { # mail originating from @mynetworks
> bypass_spam_checks_maps => [1], # don't spam-check internal mail
> bypass_banned_checks_maps => [1], # don't banned-check internal mail
> bypass_virus_checks_maps => [1], # don't banned-check internal mail
> bypass_header_checks_maps => [1], # don't banned-check internal mail
> terminate_dsn_on_notify_success => 0,
> final_spam_destiny => D_PASS,
> final_banned_destiny => D_PASS,
> };
Looks good, assuming that your internal network is 10.0.0.0/8.
The final_*_destiny=>D_PASS is probably redundant, but does not hurt.
> The MTA setup is fairly typical postfix 2.1.5 (Debian sarge), with this
> in master.cf (snipped):
>
> smtp inet n - - - - smtpd
> -o content_filter=smtp-amavis:[127.0.0.1]:10024
> 10.1.0.5:25 inet n - - - - smtpd
> -o content_filter=smtp-amavis:[127.0.0.1]:10024
> pickup fifo n - - 60 1 pickup
> -o content_filter=smtp-amavis:[127.0.0.1]:10024
> smtp-amavis unix - - n - 4 lmtp
> -o lmtp_data_done_timeout=1200
> -o lmtp_send_xforward_command=yes
> -o disable_dns_lookups=yes
Looks good.
> This is in main.cf:
>
> smtpd_authorized_xforward_hosts = 127.0.0.1/8 10.0.0.1/8
> lmtp_send_xforward_command = yes
> smtp_send_xforward_command = yes
Shouldn't this be lmtpd_authorized_xforward_hosts ?
> I actually think (based on amavisd debugging) that postfix is not sending
> XFORWARD when it connects to amavisd-new, but I can't figure out why
> that would be. amavisd-new advertises XFORWARD capability, and
> other hosts try to use it, but postfix's lmtp client doesn't seem
> to be trying, and it should for postfix 2.1, from what I can tell.
>
> I also realize that this is more of a postfix question than
> an amavisd-new one, but I hoped someone may have come across
> this and have the quick fix.
The xforward support for LMTP was added with Postfix 20031214.
I believe it is in 2.1 (but not in 2.0).
At log level 5 you should be seeing something like:
tail -f /var/log/amavisd-debug.log | grep -i xforward
(41894-07) ESMTP> 250 XFORWARD NAME ADDR PROTO HELO
(41894-07) ESMTP< XFORWARD NAME=xxx ADDR=xxx\r\n
(41894-07) switch_to_my_time 480 s, SMTP XFORWARD received
(41894-07) ESMTP> 250 2.5.0 Ok XFORWARD
(41894-07) ESMTP< XFORWARD PROTO=ESMTP HELO=xxx\r\n
(41894-07) switch_to_my_time 480 s, SMTP XFORWARD received
(41894-07) ESMTP> 250 2.5.0 Ok XFORWARD
Mark
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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/
