[Mailman-Developers] [PATCH] Fix endless prefix adding with q-p/base64 Subject lines

[Mikhail Zabaluev]

Hello Ben,

On Mon, Apr 08, 2002 at 06:10:20PM +0900, Ben Gertzfield wrote:
>
> On Monday, April 8, 2002, at 05:42 , Mikhail Zabaluev wrote:
> 
> >Finally it's getting fixed. Still though, there is a possibility of
> >the prefix being scattered between encoded/ASCII chunks; this code
> >will not find it then. I haven't seen yet if this case is realistic or
> >not.
> 
> We might be able to fix this by making email.Header.decode_header() take 
> an optional flag to merge un-encoded (us-ascii) header chunks with the 
> next adjacent chunk, since we assume that all charsets have us-ascii as 
> a strict subset.

Broad assumptions stink :)
Why not Unicode, however? It would be nice if email.Header.Header
objects would dump themselves into Unicode strings, so that we
can match regex there without hassle. See my feature request
at SF for mimelib.

> I do not think this case is particularly realistic, though.  I've 
> certainly never seen any mailer that would split in the middle of the 
> prefix and encode half of it, but who knows.

Indeed. And anyone can set prefixes with spaces, mixed languages
and so on.

-- 
Stay tuned,
  MhZ                                     JID: mookid@jabber.org
___________
Fun Facts, #14:
	In table tennis, whoever gets 21 points first wins.  That's how
	it once was in baseball -- whoever got 21 runs first won.