So, yes, our records covert our entire IP space, which is way more
than we have servers for, and that is unfortunate. I've had an open
bug for a couple of years to fix this, but the _netblocks thing is
used by things other than SPF, so it's complicated.
-all is just plain silly.
If you want to
Aside from the evil's of forwarding, and the methods that are available
to do that without running afoul of SPF.. that is an argument for
another day. Every modern email client now supports checking multiple
mailboxes don't they ;)
...
host -t TXT gmail.com
gmail.com descriptive text
Tighter how?
spf_checker_util: output header: softfail (google.com: domain of
transitioning ptp...@gmail.com does not designate 58.64.196.210 as
permitted sender) client-ip=58.64.196.210;
You want it to just fail? That would be silly, we expect people to
forward email.
I'll pass on your
Be interesting to know if they made changes, but no matter what..
"Kudos' and hats off.."
Now if we can only convince them to have tighter SPF records ;)
Return-Path:
Received: from aton.hk (HELO mail.aton.hk) (58.64.196.210)
(Dont' worry, still goes to spam folder but..