From kde-core-devel  Fri Apr 04 23:32:50 2003
From: Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date: Fri, 04 Apr 2003 23:32:50 +0000
To: kde-core-devel
Subject: Re: ANNOUNCE: mailman 2.1 on kde.org
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=104950030914298
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_jYhj+iTAsRmWnAs"


--Boundary-02=_jYhj+iTAsRmWnAs
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Friday 04 April 2003 15:34, Stephan Kulow wrote:
> Please note that I updated mailman to 2.1 today (it took a bit
> longer than I expected unfortunately ;(
>
> This version handles the outgoing mail a bit differently and I also
> removed all custom patches we had applied to our old mailman
> (to make it easier to do updates).

Argh. This new mailman apparently adds mailing-list footers (like the=20
one for the KMail mailing-list and the kde-pim ml) as text/plain=20
message part unless a message is text/plain (in this case the footer is=20
simply appended to the message body). This has two effects:
=2D The mailing-list footer is put into a frame in current KMail (because=20
all text/plain attachments which are displayed inline are put into a=20
nice frame to separate them from the message body and to make saving=20
easy by providing the filename in the header of the frame). This looks=20
a bit ugly and could be fixed by omitting the frame in case the=20
text/plain message part doesn't have a (file-)name.
=2D PGP/MIME signed messages are now displayed as partly signed because=20
multipart/signed messages are converted to multipart/mixed messages=20
with a multipart/signed message part and a text/plain message part (the=20
mailing list footer).

The first problem can easily be worked around. But the second problem=20
can't be worked around since such a mangled message doesn't look=20
different from a normal multipart/signed message with an unsigned=20
attachment.

I'd very much appreciate if this IMO wrong behavior of mailman could be=20
turned off. In the past mailman always simply appended the footer at=20
the end of the message and as everything after the closing boundary of=20
a multipart/* message is ignored this wasn't a problem. Of course the=20
footer wasn't shown for multipart/* messages because of this. But I=20
think that the new behavior is much worse.

Regards,
Ingo


--Boundary-02=_jYhj+iTAsRmWnAs
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+jhYjGnR+RTDgudgRAoOxAJ0fsC6BO9rnPrmXBkbFnwFx858tsgCfeAIc
EoEx6XR+oi27csySt/71TD8=
=+iM2
-----END PGP SIGNATURE-----

--Boundary-02=_jYhj+iTAsRmWnAs--