On Thu, 9 Oct 2008, Tomasz Chmielewski wrote:

Duane Hill schrieb:
On Thu, 9 Oct 2008, Tomasz Chmielewski wrote:

McDonald, Dan schrieb:
On Thu, 2008-10-09 at 12:07 +0200, Tomasz Chmielewski wrote:
I have a mail setup, where the SMTP server (Postfix) is running on a machine with a public IP address, and amavisd-new and spamassassin are running on a "filter" server in a private LAN.

You need to add the public and private IP's of your external box to
trusted_networks.

In local.cf, I already have:


trusted_networks 192.168.113.
trusted_networks my_external_ip
internal_networks 192.168.113.

Do you:

clear_trusted_networks
clear_internal_networks

before you set them?

No, I did not. But I just did to make sure, and it doesn't change anything.
Besides, with or without "clear_...", "amavisd debug-sa" shows:

[25472] dbg: received-header: parsed as [ ip=77.180.129.147 rdns=koln-4db48193.pool.einsundeins.de helo=tomek by=mx03.syneticon.net ident= envfrom= intl=0 id= auth= msa=0 ] [25472] dbg: received-header: relay 77.180.129.147 trusted? no internal? no msa? no [25472] dbg: metadata: X-Spam-Relays-Trusted: [25472] dbg: metadata: X-Spam-Relays-Untrusted: [ ip=77.180.129.147 rdns=koln-4db48193.pool.einsundeins.de helo=tomek by=mx03.syneticon.net ident= envfrom= intl=0 id= auth= msa=0 ] [25472] dbg: metadata: X-Spam-Relays-Internal: [25472] dbg: metadata: X-Spam-Relays-External: [ ip=77.180.129.147 rdns=koln-4db48193.pool.einsundeins.de helo=tomek by=mx03.syneticon.net ident= envfrom= intl=0 id= auth= msa=0 ] Which means the IP in question (77.180.129.147) is not trusted, internal etc.


I run an SMTP server here on my workstation. This is how I have it set up and works perfect:

clear_trusted_networks
clear_internal_networks

Is your amavisd-new on an external machine to the SMTP server?

I don't use amavisd-new. I was just talking about SpamAssassin. Have you tried running the message through SpamAssassin itself, bypassing amavisd-new? Perhaps there is a config option that is preventing the lookups. Amavisd-new does integrate into SpamAssassin directly; bypassing the need for spamc/spamd (at least I think it does).

Reply via email to