wasm-demo/demo/ermis-f/imap-protocol/cur/1600095048.22749.mbox:2,S

34 lines
1.4 KiB
Plaintext

MBOX-Line: From lyndon at orthanc.ca Mon Jan 9 16:41:24 2012
To: imap-protocol@u.washington.edu
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Date: Fri Jun 8 12:34:47 2018
Subject: [Imap-protocol] "normalized message ID" in RFC 5256?
In-Reply-To: <alpine.OSX.2.00.1201091616000.38441@hsinghsing.panda.com>
References: <67105.1326153749@parc.com>
<alpine.OSX.2.00.1201091616000.38441@hsinghsing.panda.com>
Message-ID: <8308F0D4-F021-4C79-BD18-5BB8097A0B71@orthanc.ca>
On 2012-01-09, at 16:31 PM, Mark Crispin wrote:
> Message-ID: <"bloop"@grok.this>
> and
> Message-ID: <bloop@grok.this>
>
> as the same thing. This was a protocol wart and I'm glad to see it
> declared obsolete. I wouldn't flame anyone who decided that strcmp() is
> the one and only way to compare Message-IDs. I daresay that's what most
> implementations did anyway even when RFC 822 was king.
The attempt at RFC2195-bis called this out, and nobody complained (once educated with the Mallet of Understanding). If invented today, Message-ID would have been named UUID. The semantics are identical.
--lyndon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20120109/b2d096ec/attachment.sig>