Eike Rathke wrote: > On Wednesday, 2023-02-22 00:46:19 +0200, Otto Liljalaakso wrote: > > > Ok, I found the other parts of the thread now. > > Something strange is going on here - it seems that when Arthur replies, > > threading breaks and I see separate subthreads in Thunderbird. > > Also lists.fedoraproject.org seems to be similarly confused. > > That's likely because > | User-Agent: HyperKitty on https://lists.fedoraproject.org/ > writes broken References and In-Reply-To headers: > > | References: < > | > <bn8pr15mb2753b3d37dc3d2006cea8bc2f2...@bn8pr15mb2753.namprd15.prod.outlook.com>> > | In-Reply-To: < > | > <bn8pr15mb2753b3d37dc3d2006cea8bc2f2...@bn8pr15mb2753.namprd15.prod.outlook.com>> > > Note the doubled <<>> and folding line break after first <.
Yes, it looks like Hyperkitty has trouble with unfolding folded header fields. Kenneth's Message-ID fields are folded over two lines. That's unusual but perfectly valid syntax. It's even recommended by RFC 5322 because Kenneth's message IDs are rather long. This line folding seems to trigger some defect in Hyperkitty so that it fails to recognize the message ID each time somebody replies to Kenneth, and shows the reply as a separate thread. And then, when Artur uses Hyperkitty to reply to Kenneth, Hyperkitty seems to think the line break is part of the message ID, which results in that invalid syntax. That's just one example of how difficult it is to write a correct email parser. It's even a rather simple case compared to the monstrosities that are allowed in valid email syntax. Björn Persson
pgp1A9BxCsgXQ.pgp
Description: OpenPGP digital signatur
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
