Matt Kettler wrote:
Chris Purves wrote:
Matt Kettler wrote:
Chris Purves wrote:
I am running spamassassin 3.1.0 on Debian Sarge and I just installed the
correct packages to get rid of missing .pm file errors from spamd.log
during SPF checking. Now I am seeing:
Wed Feb 1 12:20:12 2006 [9646] error: no response
in spamd.log for most messages. I believe that it is related to SPF
checking. How can I test if SPF checking is working on my system?
This message should hit SPF_PASS. Check your X-Spam-Status and see.
There haven't been any SPF_* hits for any messages.
Then SPF isn't working, try running the copy of this message that comes to you
direct (with a return-path of evi-inc.com, instead of apache.org) through
spamassassin -D and see if SPF prints anything helpful.
Okay, here's the output from debug:
[31302] dbg: spf: message was delivered entirely via trusted relays, not
required
[31302] dbg: spf: message was delivered entirely via trusted relays, not
required
[31302] dbg: spf: relayed through one or more trusted relays, cannot use
header-based Envelope-From, skipping
[31302] dbg: spf: def_spf_whitelist_from: could not find useable
envelope sender
[31302] dbg: spf: spf_whitelist_from: could not find useable envelope sender
Return-path: <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
aurora.northfolk.ca
X-Spam-Level:
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00
autolearn=unavailable version=3.1.0
X-Spam-Report:
* -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
* -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
* [score: 0.0000]
It says that it doesn't run spf checks for trusted networks...so I guess
it's time to set that. I set for my local network in local.cf then run
again with debug:
[31337] dbg: spf: checking HELO (helo=xanadu.evi-inc.com, ip=208.39.141.86)
[31337] dbg: spf: query for /208.39.141.86/xanadu.evi-inc.com: result:
none, comment: SPF: domain of sender xanadu.evi-inc.com does not
designate mailers
[31337] dbg: spf: checking EnvelopeFrom (helo=xanadu.evi-inc.com,
ip=208.39.141.86, [EMAIL PROTECTED])
[31337] dbg: spf: query for
[EMAIL PROTECTED]/208.39.141.86/xanadu.evi-inc.com: result: pass,
comment: Please see
http://spf.pobox.com/why.html?sender=mkettler%40evi-inc.com&ip=208.39.141.86&receiver=aurora.northfolk.ca:
208.39.141.80/28 contains 208.39.141.86
[31337] dbg: spf: def_whitelist_from_spf: [EMAIL PROTECTED] is not in
DEF_WHITELIST_FROM_SPF
[31337] dbg: spf: whitelist_from_spf: [EMAIL PROTECTED] is not in
user's WHITELIST_FROM_SPF
Return-path: <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
aurora.northfolk.ca
X-Spam-Level:
X-Spam-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,
FORGED_RCVD_HELO,SPF_PASS autolearn=unavailable version=3.1.0
X-Spam-Report:
* 0.1 FORGED_RCVD_HELO Received: contains a forged HELO
* -0.0 SPF_PASS SPF: sender matches SPF record
* -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
* [score: 0.0000]
* -0.7 AWL AWL: From: address is in the auto white-list
And now it works. Thanks for your help, Matt. I feel a little stupid
now, since I should have been able to figure that out for myself.
I don't know how to get the output from spamassassin to write to a file.
The only way I have been able to get the info so far is to run "at
now" and have the output mailed to me.
Thanks again.
--
Good day, eh.
Chris
