-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2006-03-23 02:50, william(at)elan.net wrote:
And yes, some administrators regularly add "." to the end of domain
specification to signify its FQDN and not local hostname to be
searched within domains specified in /etc/resolv Resolvers all deal
with this nicely.
Per RFC 1034, they are required to - as well as applications which
ride on top of those resolvers.
So I need direction here. Do we want to consider existing SPF records
with redirect (that end with ".") at the end to be syntax error now
or do
we want some kind of last pre-RFC publication effort to correct SPF
spec and allow for it?
Please lets have comments from those who have implemented the spec
as to how you handle it (so the spec meets majority deployment when
published).
I think that the only way to enforce such a rule requires
extra-curricular effort to syntax check domain specifications such as
Scott's tool does but M::S::Q does not (for examples). Such extra
complication does not work in SPF's favor IMO.
- --Kurt
- --
Kurt Andersen <kurta(_at_)agilent(_dot_)com>
Agilent Technologies Postmaster
Global Messaging Team, Agilent Technologies
+1 (509) 921-3792
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEIth88aJC5m0EgMURAl29AJ9KjLSyeLw2z2kXAEfPb/slbdVnYwCeJD+x
83q4xD1N3NojUTCusrUR6gU=
=Wx3A
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com