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

42 lines
1.5 KiB
Plaintext

MBOX-Line: From blong at google.com Thu Jul 17 15:05:19 2014
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun 8 12:34:53 2018
Subject: [Imap-protocol] Gmail IMAP and X-GM-MSGID
In-Reply-To: <CAMMeFX5dySxGS4XwxW=zyt_J+qxq++T=_Tt4DGVKAKhztJ8ZMA@mail.gmail.com>
References: <CAMMeFX5dySxGS4XwxW=zyt_J+qxq++T=_Tt4DGVKAKhztJ8ZMA@mail.gmail.com>
Message-ID: <CABa8R6sB8Hg3zeY7htPXGuQq0R3Rg9CMi31eWpZa3CyeBf4N+w@mail.gmail.com>
On Wed, Jul 16, 2014 at 7:29 PM, Christine Spang <spang@inboxapp.com> wrote:
> I know that some of the Gmail IMAP devs are on this list, so might be a
> good place to ask a few questions about what assumptions one can make about
> X-GM-MSGID with Gmail IMAP.
>
> * Is X-GM-MSGID globally unique across all of Gmail? (I assume no, given
> sharding.)
>
No.
> * Can the same message in different accounts have the same X-GM-MSGID?
>
Yes, though fairly unlikely.
> * Do X-GM-MSGID values associated with messages ever change? (Based on the
> Gmail API docs about messageId, seems not?)
>
Only in the case of a complete account re-build, which is exceedingly rare.
Maybe 100 times in the history of Gmail? And given the current message
store, probably not likely to happen every again (but never say never).
For the API, maybe we should have a UIDVALIDITY equivalent just in case.
Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20140717/5d8012eb/attachment.html>