Hi !!
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.
But the problem could also be on the client side, the SPF check tool at
check-auth(_at_)verifier(_dot_)port25(_dot_)com just gives that results:
----------------------------------------------------------
mail-from check details:
----------------------------------------------------------
Result: fail (malformed domain)
Address: david/0297929b3b(_at_)ols(_dot_)es
Header: verifier.port25.com smtp.mail=prvs=david/0297929b3b(_at_)ols(_dot_)es;
mfrom=fail (malformed domain);
SPF TXT record/s:
v=spf1 redirect=%{l}._spf.ols.es
I also supect that there are many other implementations with the same
problem.
--
Best regards ...
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. e-mail david(_at_)ols(_dot_)es
Pintor Vayreda 1 telf +34 902 50 29 75
08184 Palau-Solita i Plegamans movil +34 670 35 27 53
----------------------------------------------------------------
-------
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