I worded my post on this topic carefully. I never said that "v=spf1"
records "should not be used", nor did I suggest "throwing out the
deployment of .. SPF records".
I am against them being included as part of the standard.
We should not drag the "v=spf1" records into issues of conformance,
interoperability, future deployment and/or deprecation, etc. Let's not
complicate the situation for publishers of records even more by
throwing "v=spf1" into the mix.
I am for implementations supporting them.
Of course "v=spf1" records can be almost certainly interpreted at
"spf2.0/mailfrom". Surely, any implementation can do this trivially.
They should. But when things go wrong with "v=spf1" records, for any
reason, better for us to be able to all say: "Use the standard"
- Mark
Mark Lentczner
http://www.ozonehouse.com/mark/
markl(_at_)glyphic(_dot_)com