Mailman 2.1.4
Red Hat Linux release 7.3 (Valhalla)

We are having problems with HTML to text/plan conversion. We have
applied the fix in
http://www.mail-archive.com/[EMAIL PROTECTED]/msg14596.html
and this fixes the problem (HTML->text/plain error: 256) discussed in
that thread.

Problems remain however. Namely, if the HTML part has
Content-Transfer-Encoding: either base64 or quoted-printable, it is
the encoded data that is passed to lynx and the result is that if it's
base64, lynx does essentially nothing and if it's quoted-printable
lynx does what it can, but some tags are munged so some stuff gets
garbled.

I couldn't find anything in the FAQ or bugs list about this.

Is there anything that can be done short of doing a decode of the
encoding before passing to lynx? Are there any patches available that
address this in that or some other way?

--
Mark Sapiro <[EMAIL PROTECTED]>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Reply via email to