Matt Kettler <[EMAIL PROTECTED]> [2002-12-16 16:24:21 -0500]: > > 3) In fact, if you can avoid it, don't ever use a simple whitelist_from, > and always use a whitelist_from_rcvd whenever possible. This closes a LOT > of loopholes like the one you found here.
Hmm... Which version of SA supports whitelist_from_rcvd? I am running Duncan's Debian packaging for woody version 2.31, which I realize is old now, but still doing good service, and when I looked at the examples in 60_whitelist.cf all of the stock SA whitelists use whitelist_from and not whitelist_from_rcvd. My older source for SA had them in 10_misc.cf. Also, I could find no reference to whitelist_from_rcvd in the Mail::SpamAssassin::Conf man page. Therefore I assume this is only available in versions newer than 2.31 somewhere. Is that correct? > Basically whitelist_from_rcvd forces a check of both the from: address and > the received headers. This makes it so the whitelist cannot be spoofed > merely by substituting a from: line. It is a boolean AND? As in both From: AND in Received:? I assume it only uses the domain portion for the Received: header check? Just trying to understand how the check for the Received: header is worked in. I assume it handles the popular exim, postfix, sendmail formats. Sweet! Bob ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
