Benny,
> Feb 19 10:02:25.354 [19195] dbg: spf: cannot get Envelope-From, cannot
> use SPF
>
> is this why whitelist_from are the only one that works ?
>
> first get it to work from local.cf, if this is working move the same
> rule to sql is the right way to test
>
> if envelope-from is non default, then set it in local.cf, info here
> perldoc Mail::SpamAssassin::Conf
>
> postfix is using Return-Path, if you are using another mta you may
> change this in the settings so spf does not say it does not find
> envelope-from as above
I'm using qmail, along with qmail-scanner-st, and I just added a patch so that
qmail adds the envelope-from to the headers
It works; this is what the first header now looks like:
Received: from mail-ve0-f193.google.com (209.85.128.193)
by myserver.com (envelope-from u...@gmail.com)
with SMTP; 19 Feb 2013 22:12:37 -0000
If I run spamassassin using these params, I don't see any SPF errors:
spamassassin -D < email.msg 2>debug.log
[...]
Feb 19 17:39:22.803 [10817] dbg: spf: checking to see if the message has a
Received-SPF header that we can use
Feb 19 17:39:22.848 [10817] dbg: spf: using Mail::SPF for SPF checks
Feb 19 17:39:22.848 [10817] dbg: spf: checking HELO
(helo=falcon594.startdedicated.com, ip=69.64.33.211)
Feb 19 17:39:22.850 [10817] dbg: dns: providing a callback for id:
55831/falcon594.startdedicated.com/SPF/IN
Feb 19 17:39:22.857 [10817] dbg: spf: query for
/69.64.33.211/falcon594.startdedicated.com: result: none, comment: , text: No
applicable sender policy available
Feb 19 17:39:22.858 [10817] dbg: spf: already checked for Received-SPF headers,
proceeding with DNS based checks
Feb 19 17:39:22.858 [10817] dbg: spf: found Envelope-From in first external
Received header
Feb 19 17:39:22.858 [10817] dbg: spf: checking EnvelopeFrom
(helo=falcon594.startdedicated.com, ip=69.64.33.211, envfrom=nore...@sonico.com)
Feb 19 17:39:22.859 [10817] dbg: dns: providing a callback for id:
65122/sonico.com/SPF/IN
Feb 19 17:39:22.941 [10817] dbg: spf: query for
nore...@sonico.com/69.64.33.211/falcon594.startdedicated.com: result: fail,
comment: Please see
http://www.openspf.org/Why?s=mfrom&id=noreply%40sonico.com&ip=69.64.33.211&r=myserver.com,
text: Mechanism '-all' matched
Feb 19 17:39:22.948 [10817] dbg: spf: def_spf_whitelist_from: already checked
spf and didn't get pass, skipping whitelist check
Feb 19 17:39:22.949 [10817] dbg: rules: ran eval rule SPF_FAIL ======> got hit
(1)
Feb 19 17:39:22.950 [10817] dbg: spf: whitelist_from_spf: already checked spf
and didn't get pass, skipping whitelist check
Feb 19 17:39:23.222 [10817] dbg: rules: ran uri rule __LOCAL_PP_NONPPURL
======> got hit: "http://www.openspf.org";
[...]
However, if I run spamassassin 2>&1 -D --lint | less I still see the error:
Feb 19 17:41:54.196 [11019] dbg: spf: cannot get Envelope-From, cannot use SPF
Feb 19 17:41:54.196 [11019] dbg: spf: def_spf_whitelist_from: could not find
useable envelope sender
> i noticed you are using openprotect rule set with 99% depricated rule
> sets :(
/var/lib/spamassassin/3.002005/saupdates_openprotect_com.pre
/var/lib/spamassassin/3.002005/saupdates_openprotect_com
/var/lib/spamassassin/3.002005/saupdates_openprotect_com.cf
/var/lib/spamassassin/3.003001/saupdates_openprotect_com.pre
/var/lib/spamassassin/3.003001/saupdates_openprotect_com
/var/lib/spamassassin/3.003001/saupdates_openprotect_com.cf
/var/lib/spamassassin/3.002004/saupdates_openprotect_com.pre
/var/lib/spamassassin/3.002004/saupdates_openprotect_com
/var/lib/spamassassin/3.002004/saupdates_openprotect_com.cf
/var/lib/spamassassin/3.003002/saupdates_openprotect_com.pre
/var/lib/spamassassin/3.003002/saupdates_openprotect_com
/var/lib/spamassassin/3.003002/saupdates_openprotect_com.cf
I can simply delete them, correct?
> why not just use spamassassin rule sets ?
Most likely from previous SA versions
Thanks for your help btw!
