On Monday 18 December 2006 13:11, Stuart D. Gathman wrote:
On Mon, 18 Dec 2006, Scott Kitterman wrote:
On Saturday 16 December 2006 16:03, Scott Kitterman wrote:
a:mail.example.com,
The error message was not wrong (a trailing comma is not allowed in an
FQDN), but could be clearer. I've updated pyspf to provide a more
specific error message for this case. It will now return:
Do not separate mechnisms with commas: a:mail.example.com,
I disagree with this. There is no end of bogus separators, including
non-ascii chars, that people use.
I would go along with the more specific message:
Invalid TLD: "com,"
Showing the bogus separator inside the quotes should be plain enough,
and will work no matter what garbage they used.
That's a good point. The check I added was specific to a trailing comma as
that is a common error (this isn't the first time I've seen that).
We do have an invalid TLD test now, buried in the regex for a valid FQDN, but
I think comma separate mechanism is common enough to warrant a special case.
It does make sense to break out invalid TLD from FQDN. Currently a:bob.123
returns:
Invalid domain found (use FQDN): bob.123
That, I think should return a TLD specific error message.
Scott K
-------
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/?list_id=735