On Sat, February 25, 2006 4:18 pm, jdow said: > From: "Chris Purves" <[EMAIL PROTECTED]> > >> Chris Purves wrote: >>> I am not getting SPF_ hits for most messages that I expect should pass >>> SPF. On one message when I run through spamassassin with debug I see: >>> >>> [5959] dbg: spf: checking HELO (helo=, ip=66.111.4.28) >>> [5959] dbg: spf: cannot get HELO, cannot use SPF >>> [5959] dbg: spf: checking EnvelopeFrom (helo=, ip=66.111.4.28, >>> [EMAIL PROTECTED]) >>> [5959] dbg: spf: cannot get HELO, cannot use SPF >>> >>> >>> The received header looks like: >>> >>> Received: from out4.smtp.messagingengine.com ([66.111.4.28]) >>> by aurora.northfolk.ca with esmtp (Exim 4.50) >>> id 1FCneI-0001Q8-Hs >>> for [EMAIL PROTECTED]; Sat, 25 Feb 2006 08:51:09 +0800 >>> >>> >> I found another clue... >> >> In one of my e-mails sent to this list, the header shows: >> >> X-Spam-Report: >> * 0.1 FORGED_RCVD_HELO Received: contains a forged HELO >> * -1.3 AWL AWL: From: address is in the auto white-list >> >> But if I run the same message from a user account with spamassassin -t < >> ... I get: >> >> -100 USER_IN_WHITELIST From: address is in the user's white-list >> 0.1 FORGED_RCVD_HELO Received: contains a forged HELO >> -0.0 SPF_PASS SPF: sender matches SPF record >> >> >> It looks like SPF and whitelisting (I have spamassassin set in >> whitelist_from_rcvd) are not being run when SA is called from exim, but >> it works when calling spamassassin manually. >> >> Any suggestions? > > One, does the user account have a user whitelist entry?
Not the user account, but local.cf > Two, are you using per user AWL. Yes > Three, did you restart spamassassin or whatever service is running > spamassassin? But, of course. ;-) -- Good day, eh. Chris
