[ mailman-Bugs-1712034 ] Pipermail uses MIME CTEs in HTTP

[SourceForge.net]

Bugs item #1712034, was opened at 2007-05-03 07:39
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1712034&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pipermail
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Stephen J. Turnbull (yaseppochi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Pipermail uses MIME CTEs in HTTP

Initial Comment:
CTE = Content-Transfer-Encoding = BASE64 or QP

John Papapanos writes:                                          
                    
 > Here is a URL where I created a list for testing 
 > mailman.                                             
 >                               
 > https://mail.bioacademy.gr/pipermail/testlist2/2007-May/thread.html 
  
Wow!  That's amazingly broken.  What's I'm pretty sure is happening is that the archive contains raw message content in a MIME QP or transfer-encoding, which cannot be decoded because the Content-Transfer-Encoding header has been stripped (AFAIK it's actually prohibited in HTTP, cf RFC 2616 section 19.5).  (I'm not 100% sure because I don't have access to the physical archive, only via https.)
               
The reason that the Greek text-only comes out OK is that your browser (John and I are both using Firefox) interprets the { notation in the message body as SGML entities, which are Unicode.

Presumably the reason that such content is in there in the first place is that either pipermail doesn't parse the mail (unlikely) or it reencodes use flatten or something like that.

I'll look more carefully at the code later, maybe provide a patch, but don't bet on it.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-05-04 13:36

Message:
Logged In: YES 
user_id=1123998
Originator: NO

It turns out that John was using Mailman 2.1.5. When he upgraded to 2.1.9,
these problems disappeared. See
<http://mail.python.org/pipermail/mailman-users/2007-May/056942.html>

I'm not certain, but I think this issue was fixed by changes in SVN rev.
7660 of Scrubber.py (Mailman 2.1.7).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1712034&group_id=103