You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Chris Purves <ch...@northfolk.ca> on 2006/02/25 02:53:31 UTC
SPF Error: cannot get HELO, cannot use SPF
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,
envfrom=christine@northfolk.ca)
[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 chris@northfolk.ca; Sat, 25 Feb 2006 08:51:09 +0800
There is no HELO in the received header, explaining the spamassassin
message, but what can I do about it? Is it a problem with my server while
receiving, or does it have to do with the server sending?
--
Good day, eh.
Chris
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
Matthias Fuhrmann wrote:
> On Sat, 25 Feb 2006, Chris Purves wrote:
>
> hI,
>
>
>>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,
>>envfrom=christine@northfolk.ca)
>>[5959] dbg: spf: cannot get HELO, cannot use SPF
>
>
> if i'm totaly wrong just ignore my mail :)
>
> but did you got by any chance similiar entries in your syslog like:
>
> Dec 18 00:05:44 machine spamd[6429]: Can't locate LMAP/CID2SPF.pm in
> @INC (@INC contains: lib ../lib
> ...
> /opt/gnu/lib/perl5/site_perl/5.8.3/Mail/SPF/Query.pm line 1749, <GEN16> line 2073.
>
Thanks, but I'm not seeing anything like that.
--
Good day, eh.
Chris
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Matthias Fuhrmann <Ma...@stud.uni-hannover.de>.
On Sat, 25 Feb 2006, Chris Purves wrote:
hI,
> 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,
> envfrom=christine@northfolk.ca)
> [5959] dbg: spf: cannot get HELO, cannot use SPF
if i'm totaly wrong just ignore my mail :)
but did you got by any chance similiar entries in your syslog like:
Dec 18 00:05:44 machine spamd[6429]: Can't locate LMAP/CID2SPF.pm in
@INC (@INC contains: lib ../lib
...
/opt/gnu/lib/perl5/site_perl/5.8.3/Mail/SPF/Query.pm line 1749, <GEN16> line 2073.
i googled and found http://www.baschny.de/spf/LMAP-CID2SPF-0.9.tar.gz
after a while. couldnt find it anywhere else, CPAN failed too.
played the mmodul at ...site_perl/5.8.3/LMAP/CID2SPF.pm
and the syslog message disappeared. worth a look anyway.
regards
Matthias
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
mouss wrote:
> Chris Purves a écrit :
> [snip]
>
>>What spamc calls EnvelopeFrom is the top header of the message:
>>
>>Return-path:
>><us...@spamassassin.apache.org>
>>
>>I am guessing that exim calls spamc before it adds this header so that
>>spamc has less information to work with than when running the tests.
>>
>>I'm sorry for the very long e-mail...I hope someone has a suggestion as
>>to what I can do now. I am using sa-exim inbetween exim and SA.
>>
>
>
> The Return-Path is added by the MTA when handing mail to something
> external (mostly for delivery). whether it'll give it to SA or not
> depends on how SA is integrated.
>
I have finally solved the return path problem. I am using sa-exim to
call spamassassin from exim. sa-exim adds its own return path header,
so I needed only to add the following line to local.cf:
envelope_sender_header X-SA-Exim-Mail-From
--
Good day, eh.
Chris
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by mouss <us...@free.fr>.
Chris Purves a écrit :
[snip]
>
> What spamc calls EnvelopeFrom is the top header of the message:
>
> Return-path:
> <us...@spamassassin.apache.org>
>
> I am guessing that exim calls spamc before it adds this header so that
> spamc has less information to work with than when running the tests.
>
> I'm sorry for the very long e-mail...I hope someone has a suggestion as
> to what I can do now. I am using sa-exim inbetween exim and SA.
>
The Return-Path is added by the MTA when handing mail to something
external (mostly for delivery). whether it'll give it to SA or not
depends on how SA is integrated.
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
Chris Purves wrote:
> 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,
>> envfrom=christine@northfolk.ca)
>> [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 chris@northfolk.ca; 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?
>
I believe I have found what is causing the problem, but don't yet know
how to fix it.
I added "-D spf" to spamd options. In spamd.log I see:
Mon Feb 27 11:44:32 2006 [20290] info: spamd: connection from
localhost.localdomain [127.0.0.1] at port 58443
Mon Feb 27 11:44:32 2006 [20290] info: spamd: processing message
<44...@northfolk.ca> for Debian-exim:102
Mon Feb 27 11:44:32 2006 [20290] dbg: spf: checking HELO
(helo=mail.apache.org,ip=209.237.227.199)
Mon Feb 27 11:44:32 2006 [20290] dbg: spf: query for
/209.237.227.199/mail.apache.org: result: none, comment: SPF: domain of
sender mail.apache.org does not designate mailers
Mon Feb 27 11:44:32 2006 [20290] dbg: spf: cannot get Envelope-From,
cannot use SPF
Mon Feb 27 11:44:32 2006 [20290] dbg: spf: def_spf_whitelist_from: could
not find useable envelope sender
Mon Feb 27 11:44:32 2006 [20290] dbg: spf: spf_whitelist_from: could not
find useable envelope sender
Mon Feb 27 11:44:40 2006 [20290] info: spamd: clean message (0.1/5.0)
for Debian-exim:102 in 7.8 seconds, 3480 bytes.
Mon Feb 27 11:44:40 2006 [20290] info: spamd: result: . 0 -
FORGED_RCVD_HELO
scantime=7.8,size=3480,user=Debian-exim,uid=102,required_score=5.0,rhost=localhost
.localdomain,raddr=127.0.0.1,rport=58443,mid=<44...@northfolk.ca>,aut
olearn=unavailable
Mon Feb 27 11:44:40 2006 [20280] info: prefork: child states: II
The I run "sudo -u Debian-exim spamc < ..." on the same message. This
is what is in spamd.log:
Mon Feb 27 11:48:50 2006 [20290] info: spamd: connection from
localhost.localdomain [127.0.0.1] at port 58451
Mon Feb 27 11:48:50 2006 [20290] info: spamd: processing message
<44...@northfolk.ca> for Debian-exim:102
Mon Feb 27 11:48:50 2006 [20290] dbg: spf: checking HELO
(helo=mail.apache.org,ip=209.237.227.199)
Mon Feb 27 11:48:51 2006 [20290] dbg: spf: query for
/209.237.227.199/mail.apache.org: result: none, comment: SPF: domain of
sender mail.apache.org does not designate mailers
Mon Feb 27 11:48:51 2006 [20290] dbg: spf: checking EnvelopeFrom
(helo=mail.apache.org, ip=209.237.227.199,
envfrom=users-return-38258-chris=northfolk.ca@spamassassin.apache.org)
Mon Feb 27 11:48:51 2006 [20290] dbg: spf: query for
users-return-38258-chris=northfolk.ca@spamassassin.apache.org/209.237.227.199/mail.apache.org:
result: pass, comment: Please see
http://spf.pobox.com/why.html?sender=users-return-38258-chris%3Dnorthfolk.ca%40spamassassin.apache.org&ip=209.237.227.199&receiver=aurora.northfolk.ca:
spamassassin.apache.org MX mail.apache.org A 209.237.227.199
Mon Feb 27 11:48:51 2006 [20290] dbg: spf: def_whitelist_from_spf:
users-return-38258-chris=northfolk.ca@spamassassin.apache.org is not in
DEF_WHITELIST_FROM_SPF
Mon Feb 27 11:48:51 2006 [20290] dbg: spf: whitelist_from_spf:
users-return-38258-chris=northfolk.ca@spamassassin.apache.org is not in
user's WHITELIST_FROM_SPF
Mon Feb 27 11:49:03 2006 [20290] info: spamd: clean message (-99.9/5.0)
for Debian-exim:102 in 12.7 seconds, 4019 bytes.
Mon Feb 27 11:49:03 2006 [20290] info: spamd: result: . -99 -
AWL,FORGED_RCVD_HELO,SPF_PASS,USER_IN_WHITELIST
scantime=12.7,size=4019,user=Debian-exim,uid=102,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=58451,mid=<4
40275AF.2080701@northfolk.ca>,autolearn=unavailable
Mon Feb 27 11:49:03 2006 [20280] info: prefork: child states: II
So...when called by exim, spamc cannot find EnvelopeFrom, but when
called by me after the message has been delivered it can find
EnvelopeFrom and complete the SPF check. I expect this is also the
reason that whitelist_from_rcvd doesn't work.
What spamc calls EnvelopeFrom is the top header of the message:
Return-path: <us...@spamassassin.apache.org>
I am guessing that exim calls spamc before it adds this header so that
spamc has less information to work with than when running the tests.
I'm sorry for the very long e-mail...I hope someone has a suggestion as
to what I can do now. I am using sa-exim inbetween exim and SA.
--
Good day, eh.
Chris
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
jdow wrote:
> From: "Chris Purves" <ch...@northfolk.ca>
>
>>>> 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. ;-)
>
>
> OK, and a fourth would involve making sure both spamassassin and spamd
> are running with the same set of rules. USER_IN_WHITELIST is an eval
> in 60_whitelist.cf under 3.05. I see no reason it would have changed much
> with 3.10, logically. So one might presume the spamd is running with a
> set of options such that it bypasses reading the /usr/share/spamassassin
> directory for the stock shared rules. Are you using one of the options
> that redirects the source for the rules with spamd?
I am running different versions of spamassassin (including spamd) and
spamc in order to keep a stable Debian system. Spamassassin is version
3.1.0 and spamc is version 3.0.3; however, I haven't noticed any
problems with any other rules. Network and local tests appear to be
working fine with this setup.
I'm not using any options like that to my knowledge. Besides "-d"
spamassassin is running with the following options:
-u Debian-exim --create-prefs --max-children 5 --helper-home-dir=/var/s
pool/spamassassin/ -s /var/log/spamassassin/spamd.log
> Fifth, is the directory readable by the account you are using for spamd?
>
> Sixth, is the account you are using for testing the same as the account
> for the live case you mention? (I suppose this one should have been
> question zero. I just sort of presumed this was the case. But sometimes
> the obvious questions are ones people overlook because "fer shure it's
> OK." {^_-})
I'll answer the fifth and sixth question together. I found that with
the defaul setup spamd was being run as root. Under this situation I
could manually call spamc with a local user and user Debian-exim (which
according to spamd.log is the user that normally calls spamc) and the
results shows the SPF results as well as the whitelist entry. As you
can see from above I swtiched the spamd user to Debian-exim. Manually
calling spamc (using sudo -u Debian-exim ...) under this situation works
fine, but when called directly from exim, still no good.
The only thing I can think of trying is downgrading spamassassin to
3.0.3 to match spamc and see if that works. I don't want to upgrade
spamc, because it wants to upgrade too many other packges.
--
Good day, eh.
Chris
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by jdow <jd...@earthlink.net>.
From: "Chris Purves" <ch...@northfolk.ca>
>>> 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. ;-)
OK, and a fourth would involve making sure both spamassassin and spamd
are running with the same set of rules. USER_IN_WHITELIST is an eval
in 60_whitelist.cf under 3.05. I see no reason it would have changed much
with 3.10, logically. So one might presume the spamd is running with a
set of options such that it bypasses reading the /usr/share/spamassassin
directory for the stock shared rules. Are you using one of the options
that redirects the source for the rules with spamd?
Fifth, is the directory readable by the account you are using for spamd?
Sixth, is the account you are using for testing the same as the account
for the live case you mention? (I suppose this one should have been
question zero. I just sort of presumed this was the case. But sometimes
the obvious questions are ones people overlook because "fer shure it's
OK." {^_-})
{^_^}
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
On Sat, February 25, 2006 4:18 pm, jdow said:
> From: "Chris Purves" <ch...@northfolk.ca>
>
>> 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,
>>> envfrom=christine@northfolk.ca)
>>> [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 chris@northfolk.ca; 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
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by jdow <jd...@earthlink.net>.
From: "Chris Purves" <ch...@northfolk.ca>
> 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,
>> envfrom=christine@northfolk.ca)
>> [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 chris@northfolk.ca; 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?
Two, are you using per user AWL.
Three, did you restart spamassassin or whatever service is running spamassassin?
{^_^}
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by "Barton L. Phillips" <ba...@applitec.com>.
Yes I am sure I see the -100 score effect, here is an example from this
message posted to the list:
X-Spam-Status: No, hits=-107.0 required=5.0
tests=1.6:AWL;
version=3.1.0
X-Scanned-By: MIMEDefang 2.53 on 68.122.243.210
Note that it is mimedefang and not spamassassin that is writing the X-Spam-Status
from the filter_end() function which I have modified.
I added my whitelist_from commands to my local.cf file which is in /etc/mail/spamassassin. I am sure that these
rules are being read as I have watch the startup with spamassassin -D --lint
And I have run --lint with no errors.
I know I have muddied the water a bit with mimedefang but what I do in filter_end() is pretty straight forward.
my($hits, $req, $names, $report) = spam_assassin_check();
# look at $report and take the n.n tag part out
my $myrpt = '';
for my $ln (split '\n', $report) {
next unless $ln =~ /^ *(\d+\.\d+) +(\w+) /;
$myrpt .= "$1:$2;";
}
# Regardless of hit or miss generate the X-Spam-Status
action_change_header("X-Spam-Status", &build_status_line($hits, $req, $names, $myrpt));
The build_status_line() mimics SA's output pretty much to create multiple wrapped lines of 'score:rule;...'
I write this in both ham and spam emails. The $myrpt is also written to the log file.
I have never seen the USER_IN_WHITELIST rule.
Here is what I see if I run spamassassin from the command line on this message after first doing a spamassassin -d to strip
off the headers and then doing a spamassassin <stripped-mail.eml
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on bartonphillips.com
X-Spam-Level:
X-Spam-Status: No, score=-107.0 required=5.0 tests=AWL,BAYES_00,SPF_PASS,
USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=unavailable
version=3.1.0
But not that the score=-107.0 is the same score I get via SA run by mimedefang.
If no one here has an idea I will ask on the mimedefang list.
Thanks
Matt Kettler wrote:
> Barton L. Phillips wrote:
>
>> This is a little off this post, but why don't I ever see
>> USER_IN_WHITELIST in my emails. I see the -100's affect in my
>> X-Spam-Status but I don't see the rule. I am running SpamAssassin via
>> mimedefang. Could that have something to do with it, or is there a
>> configuration option I have missed?
>>
> Hmm that seems rather odd.
>
> Are you *sure* you're seeing the -100 score effect?
>
> What exactly are you seeing in your X-Spam-Status?
>
> Where did you add your whitelist commands (what file)?
>
> Have you run "spamassassin --lint" lately?
>
>
--
----------------
Barton L. Phillips
Applied Technology Resources, Inc.
Tel: (818)652-9850
Web: http://www.applitec.com
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Matt Kettler <mk...@comcast.net>.
Barton L. Phillips wrote:
> This is a little off this post, but why don't I ever see
> USER_IN_WHITELIST in my emails. I see the -100's affect in my
> X-Spam-Status but I don't see the rule. I am running SpamAssassin via
> mimedefang. Could that have something to do with it, or is there a
> configuration option I have missed?
Hmm that seems rather odd.
Are you *sure* you're seeing the -100 score effect?
What exactly are you seeing in your X-Spam-Status?
Where did you add your whitelist commands (what file)?
Have you run "spamassassin --lint" lately?
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by "Barton L. Phillips" <ba...@applitec.com>.
This is a little off this post, but why don't I ever see
USER_IN_WHITELIST in my emails. I see the -100's affect in my
X-Spam-Status but I don't see the rule. I am running SpamAssassin via
mimedefang. Could that have something to do with it, or is there a
configuration option I have missed?
Chris Purves wrote:
> 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,
>> envfrom=christine@northfolk.ca)
>> [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 chris@northfolk.ca; 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?
>
>
>
>
--
----------------
Barton L. Phillips
Applied Technology Resources, Inc.
Tel: (818)652-9850
Web: http://www.applitec.com
Re: SPF Error: cannot get HELO, cannot use SPF
Posted by Chris Purves <ch...@northfolk.ca>.
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,
> envfrom=christine@northfolk.ca)
> [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 chris@northfolk.ca; 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?
--
Good day, eh.
Chris