Add "message_id_format" variable for customizing generated Message-IDs

[cwfoo]

What would you like to be able to do?

Add message_id_format configuration variable for customizing generated Message-IDs. This feature was implemented in Mutt 2.1.0 (2021-06-12). Mutt 2.1 Release Notes:

Message ID Format

The Mutt 2.0 release changed the default generated Message-ID format. There are all sorts of opinions about how a Message-ID ought to be generated, though, so this release created a new configuration variable: $message_id_format.

The pre-2.0 Message-ID style can be generated by setting this to "<%Y%02m%02d%02H%02M%02S.G%c%p@%f>", for instance. There are a few other expandos that may be useful, but also note that format strings can use a filter and be generated by your own script.

Mutt doesn't perform validation on the generated value; it's your responsibility to generate legal (and unique) values if you change the format string. Please be a good netizen and customize responsibly.

[gahr]

Hi, I am curious as to what is the use-case for wanting custom message-ids.

[flatcap]

This feature was implemented in Mutt

In the past, we've merged all of upstream Mutt's fixes and features, but for the last six months we've been making some large architectural improvements to the code.

We're still a bit busy.

However, if you have some C knowledge, we'd be happy to help you port any Mutt patches to NeoMutt.

If you're interested, you can also find us on IRC: #neomutt on irc.libera.chat (web client)

[iameru]

bumping. this became more relevant as for some spamfilters report +0.5 for not seeing an FQDN at the right side of the @ also here is some discussion and reasoning https://www.mail-archive.com/[email protected]/msg14723.html

for now a dirty quick fix can be found here https://people.kernel.org/monsieuricon/fix-your-mutt

this quickfix is painful though, especially when dealing with multiple mutt rcs for different mailboxes / accounts.