You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Robert S <ro...@gmail.com> on 2006/12/07 13:02:27 UTC
What is the correct way of whitelisting local mail?
I'm trying to stop SA from incorrectly labeling local messages as
spam. The most common target is a weekly script that notifies the
user of quarantined spams. The subject lines of each message fire off
a false positive.
What is the correct way of whitelisting local mail?
trusted_networks 192.168.2. 127.0.0.1 does not seem to ensure this and
whitelist_from @mydomain.com
might whitelist messages with spoofed sending addresses.
Can anybody help?
Re: What is the correct way of whitelisting local mail?
Posted by Nels Lindquist <nl...@maei.ca>.
Robert S wrote:
> I'm trying to stop SA from incorrectly labeling local messages as
> spam. The most common target is a weekly script that notifies the
> user of quarantined spams. The subject lines of each message fire off
> a false positive.
>
> What is the correct way of whitelisting local mail?
The best way, if possible, is to configure your MTA not to run
SpamAssassin on local mail traffic, however you define that.
----
Nels Lindquist
Re: What is the correct way of whitelisting local mail?
Posted by "John D. Hardin" <jh...@impsec.org>.
On Fri, 8 Dec 2006, Robert S wrote:
> > Determine what is passing messages to SA and tell it to not do that
> > with locally-sources messages. If you use procmail to launch spamc
> > this is pretty easy to do.
>
> I use procmail. I could do this in /etc/procmailrc:
>
> :0fw: spamassassin.lock
> * < 256000
> * ! From: .*mydomain.com
> | /usr/bin/spamc
>
> .. but presumably this would fail to scan messages with forged
> headers that claim to come from my network.
That's why you should check the Received: header your MTA added to see
whether it came from a local network host, or was an authenticated
user.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
The fetters imposed on liberty at home have ever been forged out
of the weapons provided for defense against real, pretended, or
imaginary dangers from abroad. -- James Madison, 1799
-----------------------------------------------------------------------
8 days until Bill of Rights day
Re: What is the correct way of whitelisting local mail?
Posted by Robert S <ro...@gmail.com>.
> Determine what is passing messages to SA and tell it to not do that
> with locally-sources messages. If you use procmail to launch spamc
> this is pretty easy to do.
I use procmail. I could do this in /etc/procmailrc:
:0fw: spamassassin.lock
* < 256000
* ! From: .*mydomain.com
| /usr/bin/spamc
.. but presumably this would fail to scan messages with forged headers
that claim to come from my network.
Re: What is the correct way of whitelisting local mail?
Posted by "John D. Hardin" <jh...@impsec.org>.
On Thu, 7 Dec 2006, Robert S wrote:
> I'm trying to stop SA from incorrectly labeling local messages as
> spam. The most common target is a weekly script that notifies the
> user of quarantined spams. The subject lines of each message fire off
> a false positive.
Determine what is passing messages to SA and tell it to not do that
with locally-sources messages. If you use procmail to launch spamc
this is pretty easy to do.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
The fetters imposed on liberty at home have ever been forged out
of the weapons provided for defense against real, pretended, or
imaginary dangers from abroad. -- James Madison, 1799
-----------------------------------------------------------------------
8 days until Bill of Rights day