On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin <inva...@pizzashack.org> wrote:
> On Sun, Apr 07, 2024 at 01:19:09PM +0000, Ебрашка wrote: > > Question, what should I write in .muttrc to make my outgoing mails have > > the same beautiful message-ID as Yandex mail? > > The unfathomable thing about this question is why you (or anyone) > should care in the slightest what your message ID looks like. It's an > esoteric detail about e-mail transfer, the specific contents of which > have no value to users, who in most cases won't even ever see the > message ID, since most mail clients hide that detail from you by > default. You have no practical reason to care what it is as long as > everything is working correctly. It's literally not for you--it's for > your MUA software. The link to a kernel mailing list message that was provided earlier in this discussion said that the choice to use base64 results in the possibility of / characters being included in the message id which causes problems for their archived messages accessible via a web browser. So it seems that there is a reason to care about this. Although one could argue that the mailing list archiving system should accept the responsibility of munging message ids to suit its own needs. I've certainly seen mailing list archives on the web that did munge the message id (but to replace @ characters, I think). cheers, raf > -- > Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. Replying to it will result in > undeliverable mail due to spam prevention. Sorry for the inconvenience. >
