On Mon, 22 May 2006, David Saez Padros wrote:
Just playing with BATV i noticed that it could conflict with
some (mine in that case) SPF setups. If i publish SPF records
like "v=spf1 redirect=%{l}._spf.ols.es" which use the local part
of the envelope sender to generate a new dns request then batv
encoded addresses like prvs=david/0297929b3b(_at_)ols(_dot_)es produce a
dns query on prvs=david/0297929b3b._spf.ols.es which include
two forbiden charactes (= and /) I noticed that some implementations
will just use david/0297929b3b._spf.ols.es for the query but this
also includes the forbiden character "/"
This problem is not only restricted to batv as the allowed email
characters do not match dns allowed characters, so many email
addresses could then not be verifiable using something like
"v=spf1 redirect=%{l}._spf.ols.es", how is this addressed
by current specs and implementations ?
There is no such charset restriction in the current DNS spec. There may be
some broken/obsolete DNS servers (e.g. M$), but yours doesn't need to be one of
them. As long as your DNS server (the one hosting / responding to your SPF
records) works, there is no problem.
BTW, the broken M$ DNS affects RDNS delegation as well as verifying
BATV/SRS/SES via DNS.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------
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