https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5452
Daniel Lemke le...@jam-software.com changed:
What|Removed |Added
CC|
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6417
--- Comment #8 from John Hardin jhar...@impsec.org 2010-07-05 15:20:23 EDT ---
Jason, John:
The !SPF_PASS change for HK_FAKENAME_MICROSOFT went live a while ago. Is
the behavior enough better that this bug can be closed?
--
Configure
There's a thread that's currently on the users list about Nationwide Bank
in UK publishing an SPF record that includes messagelabs, and messagelabs'
SPF record says +all. This makes it a little difficult to use SPF to
reject phishing.
In light of that, do we want to revisit
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5684
John Hardin jhar...@impsec.org changed:
What|Removed |Added
CC|
FWIW we've told Nationwide about this. They are including
include:messagelabs.com which should be spf.messagelabs.com. PEBCAK.
John Hardin wrote:
There's a thread that's currently on the users list about Nationwide
Bank in UK publishing an SPF record that includes messagelabs, and
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5684
--- Comment #12 from Karsten Bräckelmann guent...@rudersport.de 2010-07-05
16:04:22 EDT ---
(In reply to comment #11)
Actual example of abuse in the wild:
Not abuse. Mis-configuration.
As long as this is the case SPF cannot be used
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5684
Kevin A. McGrail kmcgr...@pccc.com changed:
What|Removed |Added
CC|
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5684
--- Comment #14 from Karsten Bräckelmann guent...@rudersport.de 2010-07-05
16:19:04 EDT ---
(In reply to comment #12)
Mis-configuration.
As long as this is the case SPF cannot be used to filter Nationwide Bank
phishing, and a
