Jasper Wallace wrote:
Indeed, how many options do we have? can we express them all using a single
letter (it would have to be case insensitive)? then we can ditch the {}'s
all together.
The problem is that the options (about 16 at the moment -- 8 lowercase +
their 8 equivalent url-encoded uppercase) have a variable number of
modifiers.
For example:
%{d2} is the last two components of the domain
%{ir} is the reversed ip address
For the local part it can be more complex:
%{ur-} is the reversed local part of the sender, split at '-'
You might argue that the url-encoding should not be based on the case of
the initial letter, but should be another modifier. Thinking about it, I
would support that - even though it would break backwards compatibility.
With appropriate definitions, then we could make the whole of the SPF
record case insensitive (as far as functionality was concerned). The
explanation would still (in a sense) be case sensitive.
Philip
-------
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;±¤Ö¤Íµø?¡