Header field name rules are in RFC 5322. That deals with case sensitivity
for field name strings. Section 1.2.2 provides the basis for knowing whether
a defined string is to be parsed in a case sensitive or insensitive manner.
That's right, and all of the fields defined in 5322 have case insensitive
names, but as far as I can tell, I could define a header like this:
pickle-header = %d80.111.99.107.108.101 ":" CFWS ( "dill" / "garlic" /
"kimchee" )
So this is a pickle-header
Pickle: dill
but this is not:
pickle: garlic
I'm not saying any sensible person would do that, but as far as I can
tell, that's what the spec says.
Regards,
John Levine, johnl(_at_)iecc(_dot_)com, Primary Perpetrator of "The Internet for
Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html