[MM3-users]mailman 2 vs. mailman 3: what happened to multipart/digest?
Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view.
It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest.
Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on?
[1] Mime Digests & Summary Digests - I didn't see any difference for those two options.
Here is a sample of mime types that I used to get with mime digest delivery in mailman 2 (notice the multipart/digest):
Content-Type: multipart/mixed; boundary="===============1472225091712365472==" Content-Type: text/plain; charset="utf-8" Content-Type: text/plain; charset="utf-8" Content-Type: multipart/digest; boundary="===============6619260109017411105==" Content-Type: message/rfc822 Content-Type: text/plain; charset=US-ASCII Content-Type: message/rfc822 Content-Type: text/plain; charset="UTF-8" Content-Type: message/rfc822 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Type: message/rfc822 Content-Type: multipart/alternative; boundary=001a11c3cab0b7b2d5052f6fcd1e Content-Type: text/plain; charset=UTF-8 Content-Type: text/html; charset=UTF-8 Content-Type: message/rfc822 Content-Type: text/plain; charset=UTF-8 . . Content-Type: text/plain; charset="utf-8"
On May 12, 2016, at 04:16 PM, deu8yz2mpq@snkmail.com wrote:
[1] Mime Digests & Summary Digests - I didn't see any difference for those two options.
There currently is no different between MIME and summary digests. We talked a long while ago about summary digests, but they've never been implemented. However, MM3 does implement RFC 1153 (i.e. "plaintext") and MIME digests and it should be possible to select your choice on your membership record, although I don't know whether this is plumbed through to Postorius.
The MIME format of MIME digests should roughly be:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
Cheers, -Barry
On 5/12/16 9:16 AM, deu8yz2mpq@snkmail.com wrote:
Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view.
This format vs. plain text digests was a user option in Mailman 2.
It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest.
The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius.
If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool.
Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on?
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/digester.html>)
If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 12, 2016, at 12:18 PM, Mark Sapiro wrote:
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there.
I'm not sure if they're exposed in mailmanclient, but they are exposed in the
core's REST API, on the member resource. It's the delivery_mode attribute
and it takes as legal values one of 'regular', 'plaintext_digests',
'mime_digests', and 'summary_digests' (IOW, the enum item names for the
DeliveryMode enum).
Cheers, -Barry
On 05/12/2016 09:26 PM, Barry Warsaw wrote:
On May 12, 2016, at 12:18 PM, Mark Sapiro wrote:
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there.
I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the
delivery_modeattribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum). They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/Cheers, -Barry
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 5/13/16 5:05 PM, Simon Hanna wrote:
On 05/12/2016 09:26 PM, Barry Warsaw wrote:
On May 12, 2016, at 12:18 PM, Mark Sapiro wrote:
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there.
I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the
delivery_modeattribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum).
They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/
You are correct. When I checked this before my initial reply, I never pulled down the Delivery Mode list to see all the options. My bad.
However, please correct me if I'm wrong, but there does not appear to be a way in Postorius to set a list's mime_is_default_digest attribute.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 05/14/2016 07:11 AM, Mark Sapiro wrote:
On 5/13/16 5:05 PM, Simon Hanna wrote:
On 05/12/2016 09:26 PM, Barry Warsaw wrote:
On May 12, 2016, at 12:18 PM, Mark Sapiro wrote:
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there.
I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the
delivery_modeattribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum).They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/
You are correct. When I checked this before my initial reply, I never pulled down the Delivery Mode list to see all the options. My bad.
However, please correct me if I'm wrong, but there does not appear to be a way in Postorius to set a list's mime_is_default_digest attribute.
You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.
On May 13, 2016, at 10:11 PM, Mark Sapiro wrote:
However, please correct me if I'm wrong, but there does not appear to be a way in Postorius to set a list's mime_is_default_digest attribute.
I think that's a legacy attribute that should probably go away. It's only defined as a column in the database and set in the default style, but it's not defined in the IMailingList interface or actually *used* anywhere.
Cheers, -Barry
Mark Sapiro wrote at 12:18 -0700 on May 12, 2016:
On 5/12/16 9:16 AM, deu8yz2mpq@snkmail.com wrote:
Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view.
This format vs. plain text digests was a user option in Mailman 2.
It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest.
The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius.
If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool.
Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on?
Thanks for the info - and Barry's reply as well. I understand that MIME digests are supported in Mailman 3 - that's what I'm using (and thanks, Barry, for the info that Summary Digests is the same right now). My quibble is that the multipart/digest encapsulation level is gone.
Barry Warsaw wrote at 15:16 -0400 on May 12, 2016:
The MIME format of MIME digests should roughly be:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
But mm 2 had:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
So was that removal intentional, a bug or ??
Maybe you're saying there is definitely an unexposed (in Postorius) knob for that in mm3.
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/digester.html>)
If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this.
Okay.
Here's an '02 reference in git to the some heritage for multipart/digest
========== commit 63d2568fe58333f8ca0b7582f74b43e775c581cd Author: bwarsaw <> Date: Thu Jul 11 22:14:25 2002 +0000
send_i18n_digests(): Let's generate MIME digests the correct way, by
wrapping each message inside the multipart/digest in a MIMEMessage
instance. We also no longer need to initialize the mimedigest
instance's payload to the empty list.
Also, when sending the digests, be sure to include isdigest=1 in the
metadata, otherwise SMTPDirect will try to tack on another footer.==========
John wrote at 16:46 -0600 on May 12, 2016:
Mark Sapiro wrote at 12:18 -0700 on May 12, 2016:
On 5/12/16 9:16 AM, John wrote:
Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view.
This format vs. plain text digests was a user option in Mailman 2.
It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest.
The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius.
If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool.
Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on?
Thanks for the info - and Barry's reply as well. I understand that MIME digests are supported in Mailman 3 - that's what I'm using (and thanks, Barry, for the info that Summary Digests is the same right now). My quibble is that the multipart/digest encapsulation level is gone.
Barry Warsaw wrote at 15:16 -0400 on May 12, 2016:
The MIME format of MIME digests should roughly be:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
But mm 2 had:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
So was that removal intentional, a bug or ??
Maybe you're saying there is definitely an unexposed (in Postorius) knob for that in mm3.
It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/digester.html>)
If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this.
Okay.
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On May 12, 2016, at 04:46 PM, deu8yz2mpq@snkmail.com wrote:
But mm 2 had:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
So was that removal intentional, a bug or ??
It's just a bug. Could you please file that on gitlab?
Cheers, -Barry
On 5/12/16 3:46 PM, deu8yz2mpq@snkmail.com wrote:
My quibble is that the multipart/digest encapsulation level is gone.
Barry Warsaw wrote at 15:16 -0400 on May 12, 2016:
The MIME format of MIME digests should roughly be:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
But mm 2 had:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
So was that removal intentional, a bug or ??
I'm sorry. I missed the point of your OP. I think it's a bug.
The doctest at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/digester.html>, the part just after "The MIME digest has lots of good stuff, all contained in the multipart." is clearly missing the multipart/digest part.
It appears that this got lost in the refactoring of the MM2 code for MM3. Please file an issue at <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me (msapiro), but it any case, I'll work on fixing it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote at 19:18 -0700 on May 12, 2016:
On 5/12/16 3:46 PM, John wrote:
But mm 2 had:
multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer)
So was that removal intentional, a bug or ??
I'm sorry. I missed the point of your OP. I think it's a bug.
The doctest at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/digester.html>, the part just after "The MIME digest has lots of good stuff, all contained in the multipart." is clearly missing the multipart/digest part.
It appears that this got lost in the refactoring of the MM2 code for MM3. Please file an issue at <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me (msapiro), but it any case, I'll work on fixing it.
https://gitlab.com/mailman/mailman/issues/234
Thanks.
participants (4)
-
Barry Warsaw -
John Hein -
Mark Sapiro -
Simon Hanna