[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-users
Subject:    Re: Question about message id
From:       Derek Martin <invalid () pizzashack ! org>
Date:       2024-04-11 22:58:39
Message-ID: 20240411230010.GB27298 () bladeshadow ! org
[Download RAW message or body]


On Thu, Apr 11, 2024 at 02:35:30PM -0700, googly.negotiator862@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. 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.


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]