Re: Non-encoded character in the subject

[Reiner Steib <reinersteib+gmane@imap.cc>]

On Tue, Oct 28 2008, Katsumi Yamaoka wrote:

> If the subject is encoded correctly when performing
> C-u C-c C-m P
> in the message buffer, the culprit is not Gnus in all likelihood.
> It might be MTA's doing.  Though it doesn't come under the case,
> Reiner's message I received from the MS Exchange POP server is
> broken as follows:
>
> Subject:
>  =?Windows-1252?Q?Non-encoded_character_in_the_subject_(was:_Emacs_21/22:_?=
>  =?Windows-1252?Q?_french_=E7_and_=C5=93)?=
> i.e.,
> Subject:
>  Non-encoded character in the subject (was: Emacs 21/22:  french ç and Å“)
>
> But no problem in the same message having reached Gmane.

Uh, this is the first time I hear that MTAs are changing the MIME
encoding of mail headers (I know about MTAs converting the
Content-Transfer-Encoding, e.g. qp <-> 8bit, of the body).

In fact, the article on Gmane has:

,----[ http://article.gmane.org/gmane.emacs.devel/105053/raw ]
| Subject: Non-encoded character in the subject (was: Emacs 21/22:  french
|  =?iso-8859-1?q?=E7?= and =?utf-8?b?xZMp?=
`----

My gcc-ed copy has:

,----[ Gcc ]
| Subject: Non-encoded character in the subject (was: Emacs 21/22:  french
|  =?iso-8859-1?Q?=E7?= and =?utf-8?Q?=C5=93=29?=
`----

Note the difference: binary vs. QP for the second encoded word.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/