[Mailman-Developers] Mailman archive and MIME

Wed, 20 Jan 1999 19:58:39 +0100

This is a multi-part message in MIME format.

------=_NextPart_000_00A0_01BE44AF.45E23210
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi.
Are there anyone on this list currently working on a MIME fix for =
mailman pipermail archiving? It currently (1.0b8) lack even the simplest =
MIME support, as far as I understand. If you browse a pipermail archive =
any MIME composed messages appears right out ugly and sometimes =
unreadable (a matter of skill of course).
There are at least two angles on this. One is that when MIME encoding =
(quoted-printable,base64) has been applied it looks messy in raw format. =
The other is that some mailers (outlook express...) can be configured to =
send multipart/alternative with message in both HTML and plain text =
versions. Looks even more messy in raw format.
I know you guys are working hard to get a stable release of 1.0 out on =
the streets. But before that happens I highly recommend to have this =
particular issue addressed somehow. My point is: making a stable release =
of a email/web based software in the year of 1999 without basic support =
for MIME is a big shame. Hopefully, I am plain wrong about the whole =
issue. May be I have missed the obvious.
Of course, it is my hope that someone already have a solution on the =
problem, or working on one.
If not, as a last resort, I may volunteer but not before a few weeks =
from now.

Comments, any?

Tomas

------=_NextPart_000_00A0_01BE44AF.45E23210
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>Are there =
anyone on this=20
list currently working on a MIME fix for mailman pipermail archiving?=20
</FONT><FONT size=3D2>It currently (1.0b8) </FONT><FONT size=3D2>lack =
even the=20
simplest MIME support, as far as I understand. </FONT><FONT =
color=3D#000000=20
size=3D2><FONT color=3D#000000 size=3D2>If you browse a pipermail =
archive any MIME=20
composed messages appears right out ugly and sometimes unreadable (a =
matter of=20
skill of course).</FONT></FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2><FONT color=3D#000000 =
size=3D2></FONT>There are at=20
least two angles on this. One is that when MIME encoding=20
(quoted-printable,base64) has been applied it looks messy in raw format. =
The=20
other is that some mailers (outlook express...) can be configured to =
send=20
multipart/alternative with message in both HTML and plain text versions. =
Looks=20
even more messy in raw format.</DIV>
<DIV>I know you guys are working hard to get a stable release of 1.0 out =
on the=20
streets.</FONT> <FONT color=3D#000000 size=3D2>But before that happens I =
highly=20
recommend to have this particular issue addressed somehow.</FONT> <FONT=20
size=3D2>My point is: making a stable release of a email/web based =
software in the=20
year of 1999 without basic support for MIME is a big shame. </FONT><FONT =

size=3D2>Hopefully, I am plain wrong about the whole issue. May be I =
have missed=20
the obvious.</FONT></DIV>
<DIV><FONT size=3D2>Of course, it is my hope that someone already have a =
solution=20
on the problem, or working on one.</FONT></DIV>
<DIV><FONT size=3D2>If not, as a last resort, I may volunteer but not =
before a few=20
weeks from now.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Comments, any?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Tomas</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00A0_01BE44AF.45E23210--