Package: lists.debian.org Tags: patch [Previously sent via direct mail a few months ago. Resubmitting via the BTS for better traceability.]
I noticed that viewing moderation approval mails in Evolution and Mutt gives different results - specifically the leading block "==============\nfor moderation\+==============\n\n" is not displayed in Evolution. Looking at the source of the message, I believe that lists.d.o is generating faulty content here and that Evolution's rendering, while arguably not ideal, is entirely valid. Specifically, the message is sent as multipart/digest and https://datatracker.ietf.org/doc/html/rfc2046#section-5.1.5 specifies that the default Content-Type for any subparts is therefore message/rfc822. Evolution thus attempts to parse the leading block as if it were RFC822 headers, finding nothing to render. The following trivial change should resolve this issue: <patch> --- /var/list/.bin/moderate 2020-02-28 17:34:04.536671446 +0000 +++ moderate 2024-11-27 18:04:52.234667457 +0000 @@ -400,6 +400,7 @@ while the remaining parts are likely unreadable without MIME-aware tools. --$mime_boundary +Content-Type: text/plain ============== for moderation </patch> FWIW, the older version of the "moderate" script produced messages with the expected structure, as the moderator instructions were in a subpart starting "Subject: Moderator Instructions". Regards, Adam
