What is to be avoided at all costs here is letting people believe that SPF
is somehow waiting on ratification by the IETF. That is the potential
killer.
I don't think people are thinking that -- we're in the process of adding
SPF support to our Declude JunkMail product (which handles mail for over
200,000 domains), and plan to do so without waiting for an
RFC. Why? Because it seems like all our customers want such a thing, and
even if they didn't, we see a need for it (we already came out with a
"hack" to allow our customers to simulate SPF for commonly abused domains
such as @hotmail.com). If it doesn't turn into an RFC, it is no less
useful. Turning it into an RFC is just a technicality.
Sure, there are some companies that won't add support unless it becomes an
RFC. But those are the companies that aren't going to be able to sell
their software -- not because it doesn't support SPF, but because they will
always be far behind in their anti-spam technology.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡