> Personally, I would say it should be "foo:=20bar". That's the only
> truly consistent answer.
We'll need to strike this sentence then:
"Copied header field values MUST immediately follow the header field
name with a colon separator (no white space permitted)"
>> So it seems that requiring all SWSP to be encoded and then
>> allowing perhaps arbitrary addition of real SWSP simply to keep
>> down line lengths may be the right thing to do.
>>
>>
>> That's what I do.
>
> Great, sounds like the two of us, at least, are on the same page.
...
> Note that the actual white space in the encoding is /not/ part of the
> original input, which is all encoded.
I'm on the same page too. That approach makes sense to me. I'm for it.
--
Arvel
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html