Fix your mutt
March 1, 2023

At some point in the recent past, mutt changed the way it generates Message-ID header values. Instead of the perfectly good old way of doing it, the developers switched to using base64-encoded random bytes. The base64 dictionary contains the / character, which causes unnecessary difficulties when linking to these messages on lore.kernel.org, since the / character needs to be escaped as %2F for everything to work properly.

Mutt developers seem completely [2]uninterested in changing this, so please save everyone a lot of trouble and do the following if you're using mutt for your kernel development needs (should work for all mutt versions):

1. Create a ~/.mutt-hook-fix-msgid file with the following contents (change "mylaptop.local" to whatever you like):

2. Add the following to your ~/.muttrc:

UPDATE: if you have mutt 2.1 or later you can alternatively set the [3]$message_id_format variable to restore the pre-mutt-2.0 behaviour:

Thanks to [4]Thomas Weißschuh for the suggestion!
__________________________________________________________________

References

2. https://gitlab.com/muttmua/mutt/-/issues/400
3. http://www.mutt.org/doc/manual/#message-id-format
4. https://public-inbox.org/meta/202302...duxz@t-8ch.de/

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