Re: Question about message id
On Thu, Apr 11, 2024 at 02:35:30PM -0700, googly.negotiator...@aceecat.org wrote: > On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote: > - if the mailing list does mess with msgid, it absolutely must do it > consistently for all copies of the message. For existing software that has problems with '/' (because it is a path separator), the solution is actually trivially simple. On the way in, replace it with one of the "specials" that are not allowed in a message ID, but IS allowed in your system's path names. On the way out, do the reverse transformation. You need only write a simple function that does each thing, and call them once, when the data is "on the way in" (from whichever source, either the RFC2822 message form or the on-disk form). Memory is cheap these days so just save both forms in your data structure and use the right one for the given context. Or don't, the perf hit will be imperceptible to the user (but it's more typing to call the function every time you need one or the other). There are probably only a handful of places you'd need to change, if you wrote suitably modular software--even in mail software, there are few cases where the message ID is at all interesting. -- Derek D. Martinhttp://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. signature.asc Description: PGP signature
Re: Question about message id
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote: > On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin > wrote: > > > On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка 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 [...] > 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. Yeah, but... > So it seems that there is a reason to care about this. I disagree, both for the actual stated case of wanting "the same beautiful message-ID as Yandex mail" and for the more general case of controlling message ID format. It's not something the USER should ever have to think about, for the reasons I said, quoted above--it's something only developers should ever have to care about, and even then only to the point where it complies with standards, which it does. If Mutt wants to accommodate broken list archive software (it IS broken, because it fails to handle the full range of decades-old standard, documented valid input values), then it should use a format that does that. No user should ever have reason to care about this. Seriously. > Although one could argue that the mailing list archiving system > should accept the responsibility of munging message ids to suit its > own needs. Indeed. But even that presupposes the design flaw that leads to the necessity of doing that. They could have simply organized the data differently (e.g. using a database, etc.) that does not have Unix path name issues. Also worth pointing out that if the software in question runs on Windows, there are additional allowed characters that cause breakage there. -- Derek D. Martinhttp://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. signature.asc Description: PGP signature
Re: Question about message id
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users 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. I believe it has to be a *syntactically* valid email address, according to the RFC. So, for example, an all-alphabetical random string would fail, because it'd lack a "@". > 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). I myself see not much wrong with a mailing list doing that, but: - others seem to feel differently, that modifying the msgid once a valid one has been generated by a MUA is gauche. And I understand that it makes some things slightly harder, especially if you use fcc or similar feature in other MUAs. - if the mailing list does mess with msgid, it absolutely must do it consistently for all copies of the message. Not like the mailman managed GNU lists where the msgid was (or still is?) munged if and only if the message was crossing a mail / news boundary. I stopped following the GNU lists because of that and I never went back. -- Ian
Re: How to delete message with purge=no?
Hello Will, On 2024-04-10 10:05:50, Will Yardley wrote: > On Wed, Apr 10, 2024 at 08:22:03PM +0800, Sadeep Madurange wrote: > > When deleting emails (with d), I get a prompt for purging them. I'd > > like to silence that prompt with 'no'. And, see the prompt when I > > change folder, or better yet, when I quit mutt. > > > > Is there a way to do this? > > If I'm understanding your question right, I think if you have > "delete=ask-yes" in your config, this will already be the case, i.e., > it should just be marking the message for deletion, and asking you > when synchronizing the mailbox, which should already only happen when > you're changing folder or quitting, unless you explicitly run > . > > Do you have any macros that might be running ? You're right. I had 'macro index,pager dd ""' in my rc. I removed the part, and now it's working the way I want. Thank you! -- Sadeep Madurange PGP: 103BF9E3E750BF7E
