On 24 Jan 2018, at 17:20 (-0500), John Hardin wrote:
On Wed, 24 Jan 2018, Dianne Skoll wrote:
At this point, I would be willing to penalize sites with bad SPF
records (syntactically invalid; more than one different SPF record
attached to the same domain, etc.) Those people really deserve
penalties because they've messed up.
Does that include "+all" or authorizing more than a class-b space
through any method, which I'd characterize as "malicious" rather than
"messed up"?
There are entities that still hold fast to their legacy Class A networks
and expose them to some degree to the world. Those who have tried to
change policy from inside such an organization might argue that a
multiple-B SPF authorization is neither malicious nor messed up in
itself, but rather merely an admission of a reality which i arguably
messed up but not at all malicious.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steady Work: https://linkedin.com/in/billcole
