On 2025-03-19 08:24, Bill Cole via mailop wrote:
I think that preserving the original is probably the right choice
Oh, if only they were. A specific example of this is that we're sending
out e.g.:
X-Discourse-Category: =?UTF-8?Q?=F0=9F=92=BC_Corporate_Events?=
List-ID: =?UTF-8?Q?fnord_|_=F0=9F=92=BC_Corporate_Events?=
=?UTF-8?Q?_<=F0=9F=92=BC-corporate-events.nord.discourse.group>?=
and we're getting a complete mess of text that's been passed through the
encoding wringer back in reports from Yahoo (only including some
relevant parts for brevity):
Content-Transfer-Encoding: 7bit
Content-Type: multipart/report; report-type=feedback-report;
boundary="-=Part.2fbe31.28ff75c36628a638.1948a78eac6.62d4ae70312e027b=-"
Subject: =?UTF-8?Q?FW:[Trading]_[=F0=9F=92=BC_Corporate?=
=?UTF-8?Q?_events]_Corporate_Events_in_January?=
--mime boundary--
Content-Type: message/rfc822
Subject: Re: [Trading] [💼 Corporate events] Corporate Events in January
charset: utf-8
content-transfer-encoding: 7bit
subject: [Trading] [ð<9f><92>¼ Corporate events] Corporate Events in January
x-discourse-category: ð<9f><92>¼ Corporate events
list-id: Trading | ð<9f><92>¼ Corporate events
<ð<9f><92>¼-corporate-events.trading.com>
^ this is a single message, not multiple
--
Michael Brown
Civilized Discourse Construction Kit, Inc.
https://www.discourse.org/
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
