# Fix your mutt
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):
On 3/2/23 9:39 AM, Ben Collver wrote:
# Fix your mutt
IMHO Mutt doesn't need to be fixed.
... 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.
This seems like a down stream implementation problem that doesn't
properly handle something that's RFC compliant.
Take this up with the lore.kernel.org webmaster / hostmaster and ask
them to set up something to more gracefully handle the "/" character.
I'm confident that they can put some sort of rewrite in place to handle
this more gracefully.
Granted, yes, everyone could reconfigure their mutt (X*Y amount of
work) or the problem could be fixed at the source (Z amount of work)
and the size is Z is likely a lot smaller than X*Y and would also fix
it for all MUA's, not just for mutt users who saw the message.
Rich <rich@example.invalid> writes:
Granted, yes, everyone could reconfigure their mutt (X*Y amount of
work) or the problem could be fixed at the source (Z amount of work)
and the size is Z is likely a lot smaller than X*Y and would also fix
it for all MUA's, not just for mutt users who saw the message.
Agreed. It’s not Mutt causing “unnecessary problems”, it’s the spec in
RFC2822. I wouldn’t disagree that the syntax it permits for message IDs
is much broader than it needs to be, but for as long as that is the
syntax, consumers of message IDs are going to have to cope with it.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 343 |
Nodes: | 16 (2 / 14) |
Uptime: | 33:06:08 |
Calls: | 7,557 |
Calls today: | 1 |
Files: | 12,733 |
Messages: | 5,655,842 |