Nick Rout wrote:
On Tue, 22 Aug 2006 19:58:59 -0400
Thanks, quick reply! (Thanks too Daryl, also quick)
So I take it USER_IN_WHITELIST also checks Return-Path? I wonder where
Return-Path is being set? Is it likely to be set by the spammer? Or is
my system adding it in somewhere (probably in error).
Anyway, yes I did whitelist my domain owing to a few false positives,
(my wife asking about money or s** or both?) Whitelisting seemed the
obvious but clearly wrong idea. The relevantt line will be this one in
/etc/spamassassin/local.cf:
whitelist_from [EMAIL PROTECTED] (yep thats my domain)
So is there any better way to do it? (Clearly there will be, but I don't
yet know what it is, your further help will be appreciated)
Hi,
You probably want to look at Mail::SpamAssassin::Conf
whitelist_from_rcvd [EMAIL PROTECTED] sourceforge.net
Use this to supplement the whitelist_from addresses with a check against
the Received headers. The first parameter is the address to whitelist,
and the second is a string to match the relay's rDNS.
This string is matched against the reverse DNS lookup used during the
handover from the internet to your internal network's mail exchangers.
It can either be the full hostname, or the domain component of that
hostname. In other words, if the host that connected to your MX had an
IP address that mapped to 'send-inghost.spamassassin.org', you should
specify "sendinghost.spamas-sassin.org" or just "spamassassin.org" here.
Although if your wife is emailing you about sex and money in the same
email...... well, I just won't go there :))
Regards,
Rick
