Mangled digests on Mailman3
So since I upgraded to Mailman3 recently, I’m getting reports of mangled digests even with with plaintext digests turned on. Running 3.2.1 from the ubuntu packages.
This list was imported from mailman 2.1.x.
Example below.
Any thoughts on how to fix this?
- Mark
mark@pdc-racing.net | 408-348-2878
From: tr*****-request@pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net> Subject: tr***** Digest, Vol 267, Issue 464 Date: October 19, 2019 at 5:49:46 PM PDT To: tr*****@pdc-racing.net <mailto:trackjunkies@pdc-racing.net> Reply-To: tr*****@pdc-racing.net <mailto:trackjunkies@pdc-racing.net>
Send tr***** mailing list submissions to tr*****@pdc-racing.net <mailto:trackjunkies@pdc-racing.net>
To subscribe or unsubscribe via email, send a message with subject or body 'help' to tr*****-request@pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net>
You can reach the person managing the list at tr*****-owner@pdc-racing.net <mailto:trackjunkies-owner@pdc-racing.net>
When replying, please edit your Subject line so it is more specific than "Re: Contents of tr***** digest..."
Today's Topics:
- Re: PGE phasing out EV-A (XXXXX)
Date: Sun, 20 Oct 2019 00:49:38 +0000 From: XXXXX Subject: [PDC] Re: PGE phasing out EV-A To: tr***** - The Single Biggest Drag On US GDP <tr*****@pdc-racing.net <mailto:trackjunkies@pdc-racing.net>> Message-ID: <0bca2bfb8e294ea5b910d7ae6d2a698c@Progent.com <mailto:0bca2bfb8e294ea5b910d7ae6d2a698c@Progent.com>> Content-Type: multipart/related; boundary="_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_"; type="multipart/alternative"
--_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: multipart/alternative; boundary="_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_"
--_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64
SGVyZSBhcmUgdGhlIFNNVUQgcmF0ZXMuIFNvY2lhbGlzbSB3b3JrcyENCg0KVGltZS1vZi1EYXkg KDUtOCBwLm0uKSBSYXRlIGRldGFpbHMNCiBOb24tc3VtbWVyDQpPY3RvYmVyIDEgLSBNYXkgMzEN Ck9mZi1wZWFrDQpNaWRuaWdodCDigJMgNSBwLm0uDQokMC4wOTY5IGtXaA0KQWxsIGRheSB3ZWVr ZW5kcyBhbmQgaG9saWRheXMNClBlYWsNCjUgcC5tLiDigJMgOCBwLm0uDQokMC4xMzM4IGtXaA0K T2ZmLXBlYWsNCjggcC5tLiAtIG1pZG5pZ2h0DQokMC4wOTY5IGtXaA0KIFN1bW1lcg0KSnVuZSAx IC0gU2VwdGVtYmVyIDMwDQpPZmYtcGVhaw0KTWlkbmlnaHQg4oCTIG5vb24NCiQwLjExNjYga1do
Etc.
Mark Dadgar writes:
So since I upgraded to Mailman3 recently, I’m getting reports of mangled digests even with with plaintext digests turned on. Running 3.2.1 from the ubuntu packages.
"Plaintext digest" refers to the encapsulation format that provides boundaries for individual messages, not to the content of the individual messages. If people are sending MIME-formatted mail, that's what will be included in the digest. If you don't want MIME-formatted mail, you need to set "collapse alternatives" to true, and probably "convert html to plain text" to true. You'll also need to set a rather draconian list of "MIME types to include" in "Content Filtering" (basically
multipart text
is what it needs to be). This will cause all attachments to be deleted, and reduce text parts to text/plain as much as possible.
This list was imported from mailman 2.1.x.
Example below.
If it's not the fact that the included message is MIME-formatted, what is alleged to be mangled? Looks standard-conforming to me.
participants (2)
-
Mark Dadgar -
Stephen J. Turnbull