SoylentNews

canopic jug [soylentnews.org] writes:

The Linux mailing list had an admonition for Mutt users to fix their Mutt configuration [kernel.org]. A recent change to that otherwise popular e-mail client has broken the way Message-ID headers are formed in Mutt. The developers have proven unwilling so far to fix it, therefore the onus falls upon Mutt's regular users to make local reconfigurations to avoid breaking the mailing lists and archives they might be participating in.

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.

Those receiving Mutt-generated messages will thank you for it, even if silently.

Previously:
(2018) (Neo)mutt F***ery with Multipart Messages [soylentnews.org]

Original Submission