On Tue, Jun 19, 2018 at 11:00 AM, Andy Smith <a.sm...@ldex.co.uk> wrote:
> Testing despite these errors the only rule I'm getting a hit on from KAM
> is JMQ_SPF_NEUTRAL_ALL
Andy, thanks for the very useful spamples! :)
Could somebody do a sanity check on the SPF record for
"ballybofeycarpets.com"?
I get a PermError, not SPF_NEUTRAL.
I checked using 2 different DNS servers.
Is that a bug, or an intentionally incomplete implementation?
If one skips the "a mx ptr" mechanisms, it would return Neutral.
In the first version of my own SPF code, I chose just to implement
the "ip4" and "include" mechanisms, on the theory that nobody in
their right mind would use the above three... and, of course, was
subsequently surprised at the high rate of non-right-mindedness. ;)
(I blame the abundant poor examples cut-and-pasted by cheap/bulk
webhosting companies.)
Occasionally, I see PermError with Really Big companies.
Typically, they do have a DMARC record, so should be receiving
reports, however I rarely see the problem(s) fixed.
If some SPF implementations are not returning PermError, that would
explain some of those.
*** Is there some generally accepted way to contact those companies?
Maybe their Postmaster?
Probably a lost cause, but it's frustrating seeing Broke Stuff. :(
- "Chip"
