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.
Originator: NO
Mailman is not doing this unless the original message contains alternative </x-flowed>
parts and content filtering is removing the part with <x-flowed>
tags.
Under some circumstances, Mailman will remove an RFC 3676 Format=Flowed /sourceforge. net/tracker/ index.php? func=detail& aid=1495122& group_id= 103&atid= 100103>.
parameter from the Content-Type: header. This is bug #1495122
<https:/
If some MTA/MDA/MUA is generating the <x-flowed> </x-flowed> tags from the
Format=Flowed parameter, then Mailman could be indirectly responsible.