On Tue, 2008-12-02 at 05:55 -0500, Matt Kettler wrote:
You need a second parameter to whitelist_from_rcvd. The second parameter
is the hostname (or fragment thereof) that should be found in the
Received: headers generated by the last internal host (ie: your mx).
This part does assume that you
I've been reading threads saying that whitelist_from is spoofable and
that I should be using whitelist_from_rcvd instead, so I checked the
three whitelist entries I use to whitelist_from_rcvd. Here is an
example:
whitelist_from_rcvd [EMAIL PROTECTED]
However, I'm getting them rejected with the
Martin Gregorie wrote:
I've been reading threads saying that whitelist_from is spoofable and
that I should be using whitelist_from_rcvd instead, so I checked the
three whitelist entries I use to whitelist_from_rcvd. Here is an
example:
whitelist_from_rcvd [EMAIL PROTECTED]
However, I'm
Martin Gregorie wrote on Tue, 02 Dec 2008 12:42:37 +:
at the end of the INSTALL document it says to
look at the USAGE document, but if this still exists it is not mentioned
on the 'Doc' page.
/usr/share/doc/spamassassin-3.2.5/USAGE
I admit I skipped over the Mail::Spamassassin::Conf
Martin Gregorie wrote on Tue, 02 Dec 2008 10:27:05 +:
I can't find anything in the wiki or on the SA website
that shows the valid arguments for whitelist_from_rcvd, so what am I
doing wrong?
Please?
http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Conf.html
Is this the
On Tue, 2008-12-02 at 11:55 +0100, Kai Schaetzl wrote:
Martin Gregorie wrote on Tue, 02 Dec 2008 10:27:05 +:
I can't find anything in the wiki or on the SA website
that shows the valid arguments for whitelist_from_rcvd, so what am I
doing wrong?
Please?
