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...@spamassassin.apache.org on 2022/08/10 14:14:36 UTC
[Bug 8022] New: SPF check with "v=spf1 -all"
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8022
Bug ID: 8022
Summary: SPF check with "v=spf1 -all"
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Windows 7
Status: NEW
Severity: normal
Priority: P2
Component: spamassassin
Assignee: dev@spamassassin.apache.org
Reporter: zandirboerd82@gmail.com
Target Milestone: Undefined
SPF_PASS is useless for records like "v=spf1 -all" since any IP address matches
this kind of a record.
Example:
https://mxtoolbox.com/SuperTool.aspx?action=spf%3aneckby.ru.com&run=toolpage
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 8022] SPF check with "v=spf1 -all"
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8022
Bill Cole <bi...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
CC| |billcole@apache.org
--- Comment #1 from Bill Cole <bi...@apache.org> ---
(In reply to Zandir Boerd from comment #0)
> SPF_PASS is useless for records like "v=spf1 -all" since any IP address
> matches this kind of a record.
>
> Example:
> https://mxtoolbox.com/SuperTool.aspx?action=spf%3aneckby.ru.com&run=toolpage
NO IP matches such a SPF record. '-all' makes a 'hard fail' the default, and
since there are no mechanisms that would cause a 'pass' in the record, all IPs
fail.
That is a valid SPF record for domains whose owners do not allow mail from
theier domain as a matter of policy.
If you have a sample of mail using 'neckby.ru.com' which SpamAssassin marked
with SPF_PASS, please provide that evidence. Otherwise, I can see no
SpamAssassin bug here.
--
You are receiving this mail because:
You are the assignee for the bug.