[ mailman-Bugs-1634504 ] Mailman blows away <x-flowed>

[SourceForge.net]

Bugs item #1634504, was opened at 2007-01-12 18:41
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&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: None
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman blows away <x-flowed>

Initial Comment:
Somebody replies to a list message, with To going to a me, and Cc going to the list.

The former has this body:

<x-flowed>

Dave Yost wrote:
> blah blah blah
</x-flowed>

Whereas the latter has this body:

Dave Yost wrote:
> blah blah blah
_______________________________________________
Foo mailing list
foo at bar.com
https://bar.com/cgi-bin/mailman/listinfo/foo


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

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-12 19:13

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

Mailman is not doing this unless the original message contains alternative
parts and content filtering is removing the part with <x-flowed></x-flowed>
tags.

Under some circumstances, Mailman will remove an RFC 3676 Format=Flowed
parameter from the Content-Type: header. This is bug #1495122
<https://sourceforge.net/tracker/index.php?func=detail&aid=1495122&group_id=103&atid=100103>.

If some MTA/MDA/MUA is generating the <x-flowed></x-flowed> tags from the
Format=Flowed parameter, then Mailman could be indirectly responsible.

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

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