Setting Spamassassin to Scan Mail from Localhost/127.0.0.1

[ke...@gtb.net]

Hi,

I'm using Spamassassin through ACLs with the Exim mailserver and have a
greylisting solution installed called Hermes.

Hermes listens on port 25 and acts as a proxy server and connects to Exim
at port 125.

The problem I am having is that when Hermes sends the message to
Exim/Spamassassin, the IP address the message comes from is showing
127.0.0.1 or localhost.  I think this is causing Spamassassin to not scan
or mark any of these messages.  When I disable the Hermes proxy, scores
are assigned again.

How do I either disable the auto-whitelisting feature or set Spamassassin
so it scans mail from the localhost IP?

I'm using Spamassassin 3.2.3 with Exim 4.68

Here is the command line for spamd

/usr/bin/spamd -d --allowed-ips=127.0.0.1 --pidfile=/var/run/spamd.pid
--max-children=5

OS

Centos 4.6 (Linux)

Thanks,

Keith Calligan

Re: Setting Spamassassin to Scan Mail from Localhost/127.0.0.1

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

keith.calligan@gtb.net wrote:
> Hi,
> 
> I'm using Spamassassin through ACLs with the Exim mailserver and have a
> greylisting solution installed called Hermes.
> 
> Hermes listens on port 25 and acts as a proxy server and connects to Exim
> at port 125.
> 
> The problem I am having is that when Hermes sends the message to
> Exim/Spamassassin, the IP address the message comes from is showing
> 127.0.0.1 or localhost.  I think this is causing Spamassassin to not scan
> or mark any of these messages.  When I disable the Hermes proxy, scores
> are assigned again.
> 
> How do I either disable the auto-whitelisting feature or set Spamassassin
> so it scans mail from the localhost IP?

SpamAssassin will scan any mail that it is passed, regardless of any IPs 
or received headers that the message may or may not contain.

Look for a solution in your Exim config, especially in how it interacts 
with the Hermes proxy.

Daryl