footer and MIME (and Jitterbug-bug) (PR#76)

[Bug Importer]

Jitterbug-Id: 76
Submitted-By: Bernhard Reiter <email address hidden>
Date: Mon, 5 Jul 1999 03:05:04 -0500
Version: None
OS: None

--QTprm0S8XgL7H0Dt
Content-Type: multipart/mixed; boundary=azLHFNyN32YCQGCU

--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi folks,
this is my fourth attempt to report this Mailman bug.

Jitterbug gave me:
| the system encountered a fatal error
| After command:=20
| Received:=20
| The last error code was: Connection refused=20

Original Jitterbug message attached.
Hope this is the correct forum. You should mention the bug-reporting
address on the web. Oh, an BTW the link to mailman on
http://www.python.org/mailman-bugs/ is broken. "http://" is
missing...
(and no feedback email address for that...)
 Bernhard
--=20
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Association for a Free Informational Infrastructure (ffii.org)

--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=xx
Content-Transfer-Encoding: quoted-printable

When adding a footer to mime messages, mailman acts dumb.

Consider a common PGP/MIME signature, then mailman will add the footer
behind the last contents mark and a good MUA will not display the text
from=
 there.
(Tested with mutt 0.95.6i.)

Possible solutions: add another MIME part with the footer or add a header
w=
ith
the information X-Footer (seems a bit silly to me, though ;) )

Encapsulate the first mime parts as a seperate mime part message/rfc822.
(Will be difficult for most MUA to decode and might not really help.)

eGroups mailsystem does it totally wrong and adds the footer to the
first contents. This breaks the PGP signature, of course and I would
consid=
er
it a serious bug.

Bernhard
(ps.: this is my third try to report this error. Mail to the user list
did'=
t go=20
through without bouncing and I had serveral Jitterbug failures. Webmaster
a=
lso never
answered.)

--azLHFNyN32YCQGCU--

--QTprm0S8XgL7H0Dt
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBN4BnLxFKNN1LD7H9AQEtygP+Ow9jaSD3GyMtdMYbFbB/hV7KzRw+dEyZ
0sE6pIQUMmllpsMVWuAHcwgGmfvgKf+/WV+Rpd4P63bRWRtZrj8SYrl2iMKOW8Op
2UGqjIWAx+Rh4Io4V+EK52h7xxKS2maPDKYrePDL/ifE0cZIDQfEzMyGpwXu7pMN
k04MohBKgcU=
=D293
-----END PGP SIGNATURE-----

--QTprm0S8XgL7H0Dt--

====================================================================
Audit trail:
Tue Jul 13 11:05:44 1999 bwarsaw moved from incoming to open

[http://sourceforge.net/tracker/index.php?func=detail&aid=214101&group_id=103&atid=100103]

[Barry Warsaw (barry)]

Mailman 2.0 still has a related bug; the regular footer and header are
tacked onto all digests, even though digests have the digest footer and
header as attachements. This has been fixed.

[Zardoz-users (zardoz-users)]

Why is this closed? It still occurs with non-DIGEST MIME messages in
2.0.13

[Barry Warsaw (barry)]

It's closed (now <wink>) because MM2.0.x is in critical --
read security -- bug fix mode only. Header and footer
attachment is done in a comletely MIME-safe way in Mailman
2.1, which is in beta testing and will be released RSN.