Umlauts are behaving badly

Bug #265396 reported by Bug Importer
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Unassigned

Bug Description

Umlaut characters and our nice scandinavic characters are behaving badly in
the pipermail archives. As an example see the archive:
http://oh3tr.ele.tut.fi/pipermail/moppe-archive/

All ä:s and ö:s are displayed like "=E4" in the message body. If
there
are those characters in the subject the subject line will appear as total
mess.

This could be corrected if those 8bit characters would be allowed to go
through the archiver as they are. At the moment the text version is also
messed with those =E4 characters.

Tested versions: up to Pipermail 0.05 (Mailman 2.0beta5).

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

Tags: pipermail
Revision history for this message
Bug Importer (bug-importer) wrote :

Yes, I would also like MIME-decoding of the subject-line in the header. I
tested the release version now, and the same behavious is still there.

Revision history for this message
Ber-users (ber-users) wrote :

Pipermail cannot handle mime messages and content encodings well. You could
also say that it is missing the most part from being a nice mail archiving
program.

Mailman also needs to be internationalised.
(Which is long overdue...but obviously somebody has to jump in there.)

So it is not really bug, it is a missing feature.
You could alternatively use a _real_ external mail archiving program.
There are two I know of (both have their own problems) monarch and
hypermail.

 Bernhard

Revision history for this message
Gisleh (gisleh) wrote :

The submitter states that "This could be corrected if those 8bit
characters would be allowed to go through the archiver as they are".
This is wrong. Mailers these days use quoted-printable encoding for 8-bit
characters, and the archiver need to be aware om MIME headers and content
encodings and decode things correctly (just like a MUA need to be).

As Bernard has already stated, this is a missing feature, but an important
one!

Revision history for this message
Barry Warsaw (barry) wrote :

I'm sure all this stuff is resolved in the latest MM2.1 betas.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.