On 12:24 Thu 27 Apr     , Alain Bench wrote:

>>package mutt
>>retitle 364941 mutt: wish less strict RFC 2047 header decoding
>>severity 364941 wishlist
>>tags 364941 patch
>>thanks
>>
>>
>>Hello Dmitry, and thank you for the report.
>>
>>On Thursday, April 27, 2006 at 0:02:52 +0400, Dmitry E. Oboukhov
>>wrote:
>>
>>   
>>
>>>in .muttrc: set rfc2047_parameters = yes
>>>
>>>
>>   The $rfc2047_parameters setting is relevant to attachment filename
>>decoding, not to subject.
>>   
>>
And why is it not relevant for subject? According to this RFC

http://www.faqs.org/rfcs/rfc2047.html

it can be applied to any message header, isn't it?

However Mutt shows the mails, which have in their bodies/attaches
print-quoted format with spaces, correctly.


>>>| Subject: =?koi8-r?Q?iXBT BBS=3A
>>>=F2=C5=C7=C9=D3=D4=D2=C1=C3=C9=CF=CE=CE=C1=D1
>>>|  =C9=CE=C6=CF=D2=CD=C1=C3=C9=D1 =C4=CC=D1 nobody=2C
>>>eet=40uvw=2Eru?=
>>>not correct showed in mutt (RFC-correct header)
>>>
>>>
>>   This encoded word contains spaces, and that's prohibited. The
>>   mailer
>>sending such invalid RFC 2047 subject is at fault. Mutt is strict on
>>that: Feature, no bug.
>>   
>>
Yoa are right. I've looked thoroughly through RFC, the spaces are really
prohibited.

>>   Now, such invalid 2047 headers are unfortunately not rare in the
>>wild, and Mutt's strictness may be seen as an annoyance. See undecided
>>pros and cons discussion in upstream wish/1062. There are 2
>>alternatives
>>for this Bug#364941 here:
>>
>>-1) Close Bug#364941 as not a Mutt bug.
>>
>>-2) Apply the attached patch relaxing strictness to spaces and tabs.
>>In
>>practice I never had a single drawback using it here in production
>>since
>>years.
>>
>>   I vote for (2) but don't decide. What do you think?
>>   
>>
There is a problem:
A lot of mailers (outlook, thebat, etc, as well as different forums)
that have russification, send mails with that very encoding of subjects.

I've looked through the RFC and found out that it is not correct, so I
even don't know what to answer.
Probably it is better to act according to the point 1, but I'll use Your
patch, thank You. :-\

With best regards
Dmitry Obukhov



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to