[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:25356] Re: [PATCH] do not use US-ASCII if there are
From:       Stefaan A Eeckels <Stefaan.Eeckels () ecc ! lu>
Date:       2005-07-11 9:43:01
Message-ID: 20050711114301.68f663ff.Stefaan.Eeckels () ecc ! lu
[Download RAW message or body]

On Mon, 11 Jul 2005 13:17:55 +0400
Antony Dovgal <tony2001@phpclub.net> wrote:

> On Mon, 11 Jul 2005 11:05:01 +0200
> Stefaan A Eeckels <Stefaan.Eeckels@ecc.lu> wrote:
> 
> > The encoding in the Subject ensures that it doesn't contain non-ASCII
> > characters which would violate the RFC. 
> 
> Right. But that's exactly what I got (i.e. non-ASCII chars in subject/headers).

That's OK - what is really there is the encoding of the non-ASCII
characters into this: =?ISO-8859-1?B?5vjl/Ck=?=, which is ASCII.
Nothing forces your MUA to display the above gibberish instead of
an ISO-8859-1 series of accented characters. The RFCs only state that
the Subject should not contain non-ASCII characters, not that they
cannot contain some kind of ASCII-based encoding.

> But wait, I'll poke my sysadmin and his stupid DSPAM, as it seems to be their's fault.

That could well be. Display the source of Hiroyuki's original message,
and check if the Subject line contains the gibberish above. If not, 
use an editor to modify the original message to have the following
Subject: line:

Subject: [sylpheed:25347] Re: [PATCH] do not use US-ASCII if there are
  non-ascii symbols in the subject (Test: =?ISO-8859-1?B?5vjl/Ck=?=

(notice the leading blanks before "non-ascii" to create a continuation).
Then display the message in Sylpheed and it should display the accented
characters in the Subject line.


Take care,

-- 
Stefaan
-- 
As complexity rises, precise statements lose meaning,
and meaningful statements lose precision. -- Lotfi Zadeh 

[prev in list] [next in list] [prev in thread] [next in thread]