K Anand wrote: >> >> >> See also: >> >> http://wiki.apache.org/spamassassin/QmailSpfPatch >> > > > I'm using qmailtoaster which is netqmail + some patches which include > a patch for spf (http://www.saout.de/misc/spf/). People are able to > use spf with qmailtoaster. This implies that envelope information > should be available at scan time. Nope.
Read the saut.de patch. There's no modification to the "received" fuction which adds Received: headers. That patch handles SPF checks entirely within Qmail. Because it handles it inside Qmail, it has no need to add information to the Received: headers. It is really a misnomer to call the patch from SpamAssassin a SPF patch. It is not a SPF patch. All it does is add envelope information to your Received: headers. This is required to let SA's implementation of SPF work, but it doesn't add anything SPF specific to Qmail. I can also tell you for sure you don't have anything equivalent to the SA patch by looking at your message header: Received: from unknown (HELO ?10.128.1.85?) (10.128.1.85) by sail-steel.com with SMTP; Fri, 16 Nov 2007 08:02:15 +0000 I don't see any envelope from clause in there. If you had the SA patch it would look like this: Received: from unknown (HELO ?10.128.1.85?) (10.128.1.85) by sail-steel.com (envelope-from [EMAIL PROTECTED]) with SMTP; Fri, 16 Nov 2007 08:02:15 +0000 If you're in doubt, try re-running a message that failed to match the whitelist through SA after its been delivered. At that point, the Return-Path should exist, and the whitelist should fire off just fine.. > > Anand >
