On Fri, Oct 24, 2003 at 12:22:08AM -0700, Justin Mason wrote:
|
| Well, all I can find is:
|
| - 2.3.3: %t should use 4-digit timezones, there's a few TZs which use
| sub-hour granularity. really.
good catch. well, the spec did say
The TZ timezone field syntax is
( '+' / '-' ) DIGIT DIGIT [ ':' DIGIT DIGIT ]
representing an offset from UTC. See ISO8601.
so the :30 is optional, but i'll add an example that shows it.
and i'll get rid of the :.
| - 3.5: "Valid syntax" examples for localpart uses "LocalPart" instead of
| all-lower-case "localpart". a nit ;)
spf is case insensitive for things like this, but i'll lowercase it to
fit with the other mechanisms.
| - 2.1: needs mention of what SPF clients should do if there's more than
| one TXT record on the domain -- presumably they should pick the first
| TXT record to begin with "v=spf${VERSION}" where ${VERSION} is a version
| of SPF they can grok?
I'll introduce concatenation:
"v=spf1 a"
"v=spf1 mx"
"v=spf1 default=deny"
would be equivalent to
"v=spf1 a mx default=deny"
Now the only remaining question is:
What do we do if we see
"v=spf1 a mx default=deny default=allow"
?
Should SPF parsers:
1) declare a syntax error and abort returning unknown?
2) use the first value?
3) use the last value?
-------
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;±¤Ö¤Íµø?¡