Question about message id

[Will Yardley]

On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> > I think some people mentioned some minor threading issues with the new
> > format?
> 
> Is that so?  I don't recall noticing anything about that... I'd love a
> pointer to some details, if anyone has that.

It's possible that it was since fixed. The issue isn't with threading
_in_ a main client, I think, but with certain web archiving software in
the case where the message-id has a "/" character.

https://people.kernel.org/monsieuricon/fix-your-mutt

> Anyway, I said then, and
> maintain now, that changing the format and making it configurable was
> pointless and added complexity without good technical justification.
> You may have just proven that. =8^)

Right, I was also fine with the old format, which is why I'm glad
there's an option to put it back. I'm not personally interested in
reviving the old argument about whether the new format is better or
worse, as long as there's a simple way to restore the old behavior with
a config option.

side note: using quotes around the template screws things up, that is,
set message_id_format="<xyz>"
vs
set message_id_format=<xyz>

results in a broken message-id with the quotes inside the angle brackets
(Message-ID: <"xyz">)

if folks think that's a bug, I'm happy to file an issue about it, though
just not using the quotes worked fine.

/w