In <015701c58343$5fe55640$840cea3c(_at_)lennon> "Craig Whitmore"
<lennon(_at_)orcon(_dot_)net(_dot_)nz> writes:
as well.
Interesting, thanks. Do you reject PermError ? Your table
says "unable to parse ip4:12.196.50.0/0", parsing this should
be not the real issue... ;-)
Bye, Frank
Well 12.196.50.0/0 is well quite incorrect and well what should I do?
For the verification tool, I would give a Warning rather than an
error. Several of the other validation tools do likewise, as does
libspf2.
For example you could also give a warning if the domain doesn't exist
for the a: and mx: mechanism, or if no A records can be found with
those mechanisms. In particular, things like a:1.2.3.4 are fairly
common, but the spec now requires that you reject it because "4" is
not a valid TLD. Instead, you could also give the helpful hint that
ip4:1.2.3.4 is probably what they want. Likewise, the use of ipv4:
instead of ip4: could be explained better than simply saying that
"ipv4 is an unknown mechanism".
-wayne