In <e94145390410041407347a7b5e(_at_)mail(_dot_)gmail(_dot_)com> "Anne P.
Mitchell, Esq. <amitchell(_at_)isipp(_dot_)com>"
<shedevil(_at_)gmail(_dot_)com> writes:
But you can't expect any one, especially a big ISP, to support a
standard which *its own proponents* can't even get their act together
to get out the door.
Excuse the bluntness and the French, but what's going to kill SPF is
all the d*cking around.
Uh, there have been for a *very* long time implementations for SPF
that support most major MTAs. For even longer, there have been good
wizards for creating SPF records.
CallerID, on the other hand, never had a public implementation,
despite being announced over a year ago. (Specs weren't released
until early this year.) SenderID only recently got it's first public
implementation and that is only for sendmail. (I wonder if it supports
things like adding the required Resent-From: header yet.)
After everything else which has happened, this is the *one* group
which I expected to be immune to paralysis by analysis.
Don't prove me wrong.
We haven't been. We have been paralysis by the IETF and the
seductive whispers from MS. Fortunately, things have moved ahead
anyway.
Really, what more do you want to see happen with SPF-classic?
-wayne