On Tue, Nov 23, 2021 at 04:40:28PM -0600, Aaron Poffenberger wrote:
> As for making the fqdn of the From-address available during Message-ID
> generation, I see value in it regardless. But it's not my software. I
> don't get to decide. I'll leave it as it always was: a suggestion.

At any rate, this is simply wrong, and Mutt should neither support nor
allow it.  RFC 2822 says:

   The "Message-ID:" field provides a unique message identifier that
   refers to a particular version of a particular message.  The
   uniqueness of the message identifier is guaranteed by the host that
   generates it (see below).
   ...
   The message identifier (msg-id) itself MUST be a globally unique
   identifier for a message.  The generator of the message identifier
   MUST guarantee that the msg-id is unique.

If you allow the user to muck with the host portion (techniqally
dot-atom-text portion) of the message ID you make it impossible to
guarantee that the message ID so generated is globally unique.  In
fact it would generally be better for Mutt to not set the message ID
*at all*, and allow the SMTP server it submits the message to, to do
that, which would guarantee uniquness so long as the SMTP server is
sane and reasonably well-behaved... but which is not Mutt's concern at
any rate.

As it stands currently, if Mutt is using the same format as the user's
domain's mail server to generate message IDs, it's possible for Mutt
and the mail server to generate the same ID for different messages. I
still maintain that allowing the user control over the message ID is a
bad idea.  In the best case, duplicate IDs make threading broken; in
the worst case it causes messages to be lost.

From https://en.wikipedia.org/wiki/Message-ID:

    No two different messages must ever have the same Message-ID. If
    two messages have the same Message-ID, they are assumed to be the
    same and one version is discarded. This can cause issues if tools
    mangle the IDs created by other tools. Such a problem has been
    reported with Google MTAs mangling Message-IDs created by Outlook,
    making it difficult to reference other messages and breaking
    threading.

-- 
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.

Attachment: signature.asc
Description: PGP signature

Reply via email to