PHWinfo - Afficher un message

01/11/2006, 02h57

In article <ac532$4547f596$c02a7def$8039@news2.tudelft.nl> Kees
Theunissen <theuniss@rijnh.nl> writes:
>Kees Theunissen wrote:
>> Per Hedeland wrote:
>>
>>>> So there is nothing wrong with your header as far as I can see.
>>>
>>>
>>>
>>> I would agree - but does the software doing the folding really "know"
>>> that? Unless it's the one inserting the header (i.e. it is actually
>>> folded to start with), this seems unlikely, in which case the folding
>>> sofware is broken.
>>
>>
>> The OP quoted a correctly folded header, so apearently the software
>> that has been used for that knew how to do it.
>
>Per,
>
>Reading your wording again; you might have a point if you mean that
>it is a new specification and that older software probably doesn't
>have any knowledge of the special handling of _this_ header.

Yes, that was more or less my point - though I wouldn't even add the
"older", it seems unlikely that any generic header-folding software
would have knowledge of specific headers that can tolerate folding
beyond what 2822 allows.

>If the header was folded in the middle of a string, by an other
>program without knowledge of this specification, that certainly
>would be against rfc2822 specifications.

And AFAIK 2822 specifications don't say "it's OK to fold some headers in
ways not described here, if it is known to not cause harm to those
headers". I.e. it would be against 2822 specifications period.

>But maybe you should say that the new protocol or specification
>would be broken if it didn't anticipate on to be expected actions
>of older solftware that isn't aware of the new specs.
>
>And a robust implementation of a new specification shouldn't take
>any risk and do the proper folding right from the beginning
>as soon as the header is inserted.

Or at least insert some whitespace, to allow folding per 2822. There are
probably some hints on this to be taken from the MIME spec for base64-
encoding of headers with non-ascii characters, I haven't checked
(i.e. it would be possible but unwise to encode the entire header as a
single =?...?B?...?= string).

--Per Hedeland
per@hedeland.org

01/11/2006, 02h57	#6
Per Hedeland Messages: n/a Hébergeur:	Re: Formatting of mail headers In article <ac532$4547f596$c02a7def$8039@news2.tudelft.nl> Kees Theunissen <theuniss@rijnh.nl> writes: >Kees Theunissen wrote: >> Per Hedeland wrote: >> >>>> So there is nothing wrong with your header as far as I can see. >>> >>> >>> >>> I would agree - but does the software doing the folding really "know" >>> that? Unless it's the one inserting the header (i.e. it is actually >>> folded to start with), this seems unlikely, in which case the folding >>> sofware is broken. >> >> >> The OP quoted a correctly folded header, so apearently the software >> that has been used for that knew how to do it. > >Per, > >Reading your wording again; you might have a point if you mean that >it is a new specification and that older software probably doesn't >have any knowledge of the special handling of _this_ header. Yes, that was more or less my point - though I wouldn't even add the "older", it seems unlikely that any generic header-folding software would have knowledge of specific headers that can tolerate folding beyond what 2822 allows. >If the header was folded in the middle of a string, by an other >program without knowledge of this specification, that certainly >would be against rfc2822 specifications. And AFAIK 2822 specifications don't say "it's OK to fold some headers in ways not described here, if it is known to not cause harm to those headers". I.e. it would be against 2822 specifications period. >But maybe you should say that the new protocol or specification >would be broken if it didn't anticipate on to be expected actions >of older solftware that isn't aware of the new specs. > >And a robust implementation of a new specification shouldn't take >any risk and do the proper folding right from the beginning >as soon as the header is inserted. Or at least insert some whitespace, to allow folding per 2822. There are probably some hints on this to be taken from the MIME spec for base64- encoding of headers with non-ascii characters, I haven't checked (i.e. it would be possible but unwise to encode the entire header as a single =?...?B?...?= string). --Per Hedeland per@hedeland.org