From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Hang entering summary buffer
Date: Wed, 04 Dec 2002 04:57:41 +0100 [thread overview]
Message-ID: <m3r8cyxwp6.fsf@defun.localdomain> (raw)
In-Reply-To: <yotlznrmijr8.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 04 Dec 2002 11:46:19 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <m38yz6zf1w.fsf@defun.localdomain>
>>>>>> Jesper Harder <harder@ifa.au.dk> wrote:
>
>> It happens because the Subject line is badly broken, it contains an
>> embedded CR/LF.
>
> AFAIK, the MIME header encoding doesn't express newlines in
> principle, so such encoded words are evil.
Yes. RFC 2047 actually mentions that you should beware of this
possibility:
Only printable and white space character data should be encoded using
this scheme. However, since these encoding schemes allow the
encoding of arbitrary octet values, mail readers that implement this
decoding should also ensure that display of the decoded data on the
recipient's terminal will not cause unwanted side-effects.
> The following patch may also be evil, but I think it or similar
> solution is needed to Gnus. How about it?
It's slighly evil :-) I don't think we should remove excessive
whitespace here (other than \n and \r).
I know that a lot of clients have broken RFC 2047 en/decoder that often
introduce spurious whitespace. But if we remove it we're breaking the
standard. If people want to clean it up, they should include
`gnus-simplify-whitespace' in `gnus-simplify-subject-functions' instead.
next prev parent reply other threads:[~2002-12-04 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 0:56 David Z Maze
2002-12-04 2:35 ` Jesper Harder
2002-12-04 2:46 ` Katsumi Yamaoka
2002-12-04 3:57 ` Jesper Harder [this message]
2002-12-04 6:44 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r8cyxwp6.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).