On Thu, Oct 23, 2003 at 06:25:03AM +0200, Rob Kaper wrote:
| After playing around a bit, I noticed an inconsistency:
|
| The draft RFC requires the TXT policy record, but both Perl's
| Mail::SPF::Query and the diagram on http://spf.pobox.com/howithelps.html
| seem to completely ignore it.
Argh, I have been swamped; I've spent the last week preparing for ISPcon
so a few mistakes on the web site made it through.
The web site material was designed with the original spf-01.txt in mind.
That is the version that Mail::SPF::Query and Mail::SPF::Publish work with.
The ASRG unification process has resulted in a new, very different, much
more expressive syntax, which I have found to my surprise much easier to
implement than the first one both in DNS and as a client library.
|
| For now, I've included both the correct _smtp_client allow/denies as well as
| the domain policy text for my primary domain. For other domains, I used
| both the include:capsi.com domain policy as a SPFinclude=capsi.com TXT for
| *.in-addr._smtp_client. This is hopelessly redundant, though, but it seems
| to be the only way to be in compliance with the draft, diagram *and* the
| Mail::SPF implementation.
|
I will spend the rest of today updating the web site and trying to bring
the Perl libraries up to date. That should resolve any inconsistencies;
the old 4.3.2.1.in-addr._smtp_client syntax is officially deprecated.
I apologize to everyone who has spent time implementing the old version
of things; I trust early adopters understand that things change.
cheers
meng
-------
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.txt
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡