You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/06/06 04:34:35 UTC

[Bug 3479] New: SPF_PASS and SPF_HELO_PASS should be reinstated

http://bugzilla.spamassassin.org/show_bug.cgi?id=3479

           Summary: SPF_PASS and SPF_HELO_PASS should be reinstated
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Rules
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: jm@jmason.org


we currently have:

header __SPF_PASS               eval:check_for_spf_pass()
header __SPF_HELO_PASS          eval:check_for_spf_helo_pass()

presumably the idea is that a user who *wants* to allow SPF passes to give
nonspam points can do:

meta SPF_PASS (__SPF_PASS)

however, that's not going to work for users on machines where spamd is used,
since they are not allowed to define rules.  instead, we should just issue
the rules with a minimal score, one that will not have any real effect unless
the user changes it with a

score SPF_PASS -2.0

or whatever.  normal users are permitted to do that.

fix attached.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug 3479] New: SPF_PASS and SPF_HELO_PASS should be reinstated

Posted by Daniel Quinlan <qu...@pathname.com>.
> presumably the idea is that a user who *wants* to allow SPF passes to give
> nonspam points can do:
> 
> meta SPF_PASS (__SPF_PASS)
> 
> however, that's not going to work for users on machines where spamd is used,
> since they are not allowed to define rules.  instead, we should just issue
> the rules with a minimal score, one that will not have any real effect unless
> the user changes it with a

This is bad logic.  The idea isn't that at all.

The idea is that the only use of the rule is as a meta rule or an
internal test feeding into a whitelist system.

Nevermind that SPF allows the From: header to be forged anyway.
 
-- 
Daniel Quinlan
http://www.pathname.com/~quinlan/