Alessandro Vesely wrote:
For a local part "Q&A" in "Q&A"@domain.example it
could break: http://domain.example/why?user=Q&A
That's a good one, it is clear why it won't work.
Okay, I guess <http://www.openspf.org/Modifier/exp>
could say a tiny bit more about this topic... ;-)
[[ Personally I think exp= and %{l} are some of the
two worst ideas in SPF, exists: and SOFTFAIL are
also dubious. Considering how many folks get mx
wrong, while Doug invents DDoS scenarios based
on mx and %{l}, I'm ready to add mx to the list,
as long as RMX stays in the credits... ;-) ]]
What about changing the section title to something like
== '''Why'''-service URL in Explanation modifiers
Which section, the remark in FAQ/I18N ? It can get
a link to Modifier/exp, and Modifier/exp can explain
the fine print of upper case macros with an example.
v=spf1 mx -all exp="See http://www.example.com/why?user=%{L}";
Hm... are quotes ok?
Yes and no, that's not how it works. exp= points to
a domain, e.g. "v=spf1 mx -all exp=go.to.example"
go.to.example has a TXT record with the explanation:
go.to.example. IN TXT "See http://www.example.com/why?user=%{L}";
HELO %{H} can also be odd if it's used in the URL
of an explanation.
Won't it come in its '--'-encoded form anyway?
Is that about punycode xn--labels ? What I meant was
a crappy HELO oem&computer - clear SMTP syntax error,
but if the receiver accepted it, and later tries to
report a FAIL with an explanation including %{H},
then it is at least transformed to oem%26computer
[dummy vs. _spf labels]
It could be clarified in the text that it doesn't
have to be "_spf". There are chances that the string
exemplified is pasted in the zone file "as is"
Which string, dummy.your.domain.example ? If an ISP
tries to use that as is it's no ISP, problem solved ;-)
(luckily, rfc2606 has been issued early enough...)
ACK, it should be updated adding the 11 IDN test TLDs.
Frank
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: http://www.listbox.com/member/archive/735/=now
RSS Feed: http://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com