mainSavannah Administration - Support: sr #110733, Emails received from...

 
 

sr #110733: Emails received from dmidecode-devel list are base64-encoded

Submitter:  Jean Delvare <khali>
Submitted:  Tue 27 Sep 2022 03:54:08 PM UTC
   
 
Category:  Savannah mail server Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  iank
Operating System:  GNU/Linux Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 05 Oct 2022 03:28:01 PM UTC, comment #4: 

Since this seems resolved I am housekeeping and closing the ticket.  If this issue continues to be a problem please either post again or email to mailman AT gnu.org with the updated information.

Bob Proulx <rwp>
Site Administrator
Tue 04 Oct 2022 08:32:08 AM UTC, comment #3: 

I did that and the base64-encoding is indeed gone, thanks for the tip.

Jean Delvare <khali>
Fri 30 Sep 2022 11:54:51 PM UTC, comment #2: 

My search result suggest that if a message has a non-ascii character,
and the list settings have subject prefix or footer addition, it will
reencode. I removed the footer, but I don't want to remove the subject
prefix, that is much more noticeable. I suggest that you do that and see
if it resolves the issue. Removing the subject prefix also keeps dkim
signatures intact, which is generally a good thing especially for a list
that sends patches so you have more indication they are authentic.

Ian Kelling <iank>
Site Administrator
Fri 30 Sep 2022 12:53:24 PM UTC, comment #1: 

Same problem on the quilt-dev list. So this is definitely not an issue with the dmidecode-devel list config, instead it has to be a general issue with Savannah's mailman or mail server configuration.

Jean Delvare <khali>
Tue 27 Sep 2022 03:54:08 PM UTC, original submission:  

The last few emails received from the dmidecode-devel list are no longer plain text, instead they are base64-encoded. Software developers definitely prefer plain-text emails as they are easier to process with a variety of tools.

Was this change made on purpose, or is it an accident? If nothing else, unconditionally base64-encoding all messages is going to make network traffic and list archives significantly larger.

The last plain-text email on the list is from September 19th, the first base64-encoded email is from September 22nd. I am the administrator of the list, and did not make any configuration change at that time. I did notice a recent change though: I stopped receiving moderation notifications.

Jean Delvare <khali>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by iank (Posted a comment)
  • -email is unavailable- added by khali (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-10-05 rwp StatusNone Done
        Assigned toNone iank
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code