[Mailman-Developers] Multipart logic bug

[Michael Heydekamp]

Hi Tokio,

Michael Heydekamp <my at freexp.de> on 07.01.04:

[...]

> true charset | charset sent | charset rcvd | Multipart
> -------------+--------------+--------------+----------
> US-ASCII     | US-ASCII     | US-ASCII     | no :-)
> ISO-8859-1   | ISO-8859-1   | ISO-8859-1   | no :-)
> ISO-8859-15  | ISO-8859-15  | ISO-8859-15  | no :-)
> US-ASCII     | ISO-8859-1   | ISO-8859-1   | no :-)
> US-ASCII     | ISO-8859-15  | ISO-8859-15  | no :-)
> ISO-8859-1   | US-ASCII     | both         | yes
> -------------+--------------+--------------+----------

[...]

> 2. I think it is OK that the last test leads to a multipart message.
>    OTOH I'm wondering if an obvious wrong US-ASCII declaration can
>    and should be corrected to the preferred_charset of the list (the
>    msg in fact contained 8bit characters).  But this may be wild
>    guessing plus that charset correction is probably not the job of
>    Mailman.

Thinking about this particular scenario again: Might it be an approach
to additionally check if the footer is in plain ASCII and if so,
concatenate it no matter what (by preserving the declared charset)?


        Michael