I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported:
For the last three REDACTED digests I have been getting unusual and unreadable characters? See example below.
Begin forwarded message:
*From: *REDACTED *Subject: *REDACTED*Digest, Vol 2453, Issue 2* *Date: *February 13, 2021 at 12:30:24 AM PST *To: *REDACTED@REDACTED *Reply-To: *REDACTED@REDACTED
�P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ [��X��ܚX�H �XH [XZ[ �[� H Y\��Y�H �] �X�X� ܂�� H� [ � ‚] [�\�\]Y\� [�ܙ‚�[�H �[� �XX� H \��ۈ X[�Y�[�� H \� ] �] [�[#<^_NSEDR_^#<ۙ\� [�ܙ‚�� [� �\ Z[�� X\�H Y ] [�\� �X�X� [�H �� ] \� [ܙH � X�Y�X [� �N� � [� � و S� Y�\� �� � ^I�� � X�� K� �N� [� \� � [\ � �� � �] \�B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB�Y\��Y�N� B� ] N� �K L� �X� � �H L ��N��� L ��N� �� � �] \� �� � �] \�]\�X˘��O��X�X� � � S�H �N� [� \� � [\ • Έ �� � [�Y[ �� � [�Y[ ]ܙ[��K�Y O��Έ � S� H �[\ ] ^Y\��� [� \�] [ۘ[ �] �ܚˈ� [� [�ܙς�Y\��Y�KRQ � Q � � KM��� M � N Q �P��PL �P �] \�]\�X˘��O�� [� U \ N� ][ \ \� �[ \�] ]�N‚X��[� \�OP\ KSXZ[ M ь P�KL�L�KM ��KP�KM��� ̌#<^_NSEDR_^#<͌ L �Y\� H [�� ��YX�� H \� Y �[[^H [� � X� \� [�� ��Y] [�� �Y�ܙH H Y� \� [� ] �Y[\� �\� Y [� �� �\�H ��\ ] H ] [ � H �\� ۙH و \� � Y [� ˈ [ [�� ]�\�] [�� H �]�H YK �\� [� ]�Y X[ \ \�� [� �\�[ [�� �X� [ۜˈ H �\�[ [�� �X� [ۋ �H �\� �\� H [�� [\ ܝ [� [� �[ XX� H \� � H ۸�&] [�� H �]�H [ و \� � Y [� � H �[YH X] \�X[ ˈ ] �\� H ]X� [ܙH \�#<^_NSEDR_^#<ۘ[ ^�Y \ ��X� �܈ XX� � Y [� � H ��Y� \� ���� �] H [� ܚ] [� � Y� H �]�H YH H \�� Y [� ]�[� ] � �� Y\� [�H ]�H � �H � � ۛ�� Y� ] \�JK ��\� �܈ �^[ۙ ] � [��� �� � �] \��[� ��H ^H T ۙB� ۈ �X� L
So the questions I have are:
Why does the formatting of digests change for some members when coming from MM2 to MM3?
What proble does the above example reveal?
What is the best approach to mitigate these issues?
What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do?
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/16/21 7:56 AM, Brian Carpenter wrote:
I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported:
For the last three REDACTED digests I have been getting unusual and unreadable characters? See example below.
Begin forwarded message:
*From: *REDACTED *Subject: *REDACTED*Digest, Vol 2453, Issue 2* *Date: *February 13, 2021 at 12:30:24 AM PST *To: *REDACTED@REDACTED *Reply-To: *REDACTED@REDACTED
�P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ ...
So the questions I have are:
- Why does the formatting of digests change for some members when coming from MM2 to MM3?
Could this be <https://gitlab.com/mailman/mailman/-/issues/473>? That should be fixed in Core 3.3.3.
- What proble does the above example reveal?
Insufficient headers to begin to guess.
- What is the best approach to mitigate these issues?
Depends what the issue is. The two most obvious approaches are upgrade to Mailman 3.3.3 if you aren't already there and switch from plain to MIME digests, but I would really like to see the full raw source of this digest messages to try to see if there is some other issue.
What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do?
It will probably help, but if this is Mailman 3.3.3, there's still a bug somewhere that needs to be diagnosed and fixed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/16/21 5:21 PM, Mark Sapiro wrote:
Depends what the issue is. The two most obvious approaches are upgrade to Mailman 3.3.3 if you aren't already there and switch from plain to MIME digests, but I would really like to see the full raw source of this digest messages to try to see if there is some other issue.
What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do? It will probably help, but if this is Mailman 3.3.3, there's still a bug somewhere that needs to be diagnosed and fixed.
Hi Mark,
The beginning of my OP stated I was using Mailman 3.3.3.
Remember to use your reading glasses old man!
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/16/21 2:28 PM, Brian Carpenter wrote:
The beginning of my OP stated I was using Mailman 3.3.3.
Then please get me a copy of the complete raw digest message so I can try to find the underlying issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/16/21 6:13 PM, Mark Sapiro wrote:
The beginning of my OP stated I was using Mailman 3.3.3. Then please get me a copy of the complete raw digest message so I can
On 2/16/21 2:28 PM, Brian Carpenter wrote: try to find the underlying issue.
Not sure how to do that. Do you mean have the list member forward their garbled digest message to me? Is that what you need?
-- Brian Carpenter Harmonylists.com Emwd.com
On 2/16/21 4:08 PM, Brian Carpenter wrote:
On 2/16/21 6:13 PM, Mark Sapiro wrote:
The beginning of my OP stated I was using Mailman 3.3.3. Then please get me a copy of the complete raw digest message so I can
On 2/16/21 2:28 PM, Brian Carpenter wrote: try to find the underlying issue.
Not sure how to do that. Do you mean have the list member forward their garbled digest message to me? Is that what you need?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/16/21 4:08 PM, Brian Carpenter wrote:
On 2/16/21 6:13 PM, Mark Sapiro wrote:
The beginning of my OP stated I was using Mailman 3.3.3. Then please get me a copy of the complete raw digest message so I can
On 2/16/21 2:28 PM, Brian Carpenter wrote: try to find the underlying issue.
Not sure how to do that. Do you mean have the list member forward their garbled digest message to me? Is that what you need?
Oops. Sorry for the prior content free reply.
Yes the list member needs to forward the garbled digest to you to resend to me or to me directly, but if it's forwarded, it must be forwarded as an attachment, not inline, because inline forwarding will lose the headers I need to see. Alternatively, the list member can view the message source (how to do that depends on the MUA), select it in its entirety, copy and paste it into a message to you or me
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Brian Carpenter -
Mark Sapiro