47 lines
2.8 KiB
Plaintext
47 lines
2.8 KiB
Plaintext
MBOX-Line: From brong at fastmail.fm Fri Jun 14 19:29:09 2013
|
|
To: imap-protocol@u.washington.edu
|
|
From: Bron Gondwana <brong@fastmail.fm>
|
|
Date: Fri Jun 8 12:34:51 2018
|
|
Subject: [Imap-protocol] Synchronizing multiple mailbox
|
|
In-Reply-To: <966C226A-BF79-453E-8759-6CEBBC8DFACF@iki.fi>
|
|
References: <CALog5aJ4rz8J7UxY3FPNoxVVHe1cMex3QR8PPvfB2_A9FVudJw@mail.gmail.com>
|
|
<1371204522.10116.140661243848077.263DB050@webmail.messagingengine.com>
|
|
<2C3638E0-49E6-4F8B-B998-7923F5FFEA8A@iki.fi>
|
|
<1371213398.8438.140661243890973.11ABE89B@webmail.messagingengine.com>
|
|
<6F96B898-B612-4272-B322-7A693E1CE35D@iki.fi>
|
|
<1371246156.572.140661244082645.7D3937BB@webmail.messagingengine.com>
|
|
<966C226A-BF79-453E-8759-6CEBBC8DFACF@iki.fi>
|
|
Message-ID: <1371263349.15443.140661244139353.6DEC2193@webmail.messagingengine.com>
|
|
|
|
On Sat, Jun 15, 2013, at 07:49 AM, Timo Sirainen wrote:
|
|
> On 15.6.2013, at 0.42, Bron Gondwana <brong@fastmail.fm> wrote:
|
|
>
|
|
> > On Sat, Jun 15, 2013, at 03:55 AM, Timo Sirainen wrote:
|
|
> >> On 14.6.2013, at 15.36, Bron Gondwana <brong@fastmail.fm> wrote:
|
|
> >>
|
|
> >>> On Fri, Jun 14, 2013, at 10:22 PM, Timo Sirainen wrote:
|
|
> >>>> On 14.6.2013, at 13.08, Bron Gondwana <brong@fastmail.fm> wrote:
|
|
> >>>>
|
|
> >>>>> We cheat at FastMail - we've got a patched Cyrus server which uses a single HIGHESTMODSEQ counter per user, as well as a single MAXUIDVALIDITY. Since we always bump the UIDVALIDITY of folders on rename, create or delete (keeping a tombstone record), we only need to keep track of two numbers - one for any changes to the folder listing, and a second for any changes to any mailbox. This allows us to optimise our web interface significantly (and provide the same advantages to any future clients that talk to our JSON API directly).
|
|
> >>>>
|
|
> >>>> Won't the UIDVALIDITY change on RENAME invalidate the local cache even for the client that issued the RENAME command?
|
|
> >>>
|
|
> >>> It has no guarantee anyway. You can't keep the UIDVALIDITY on rename if the destination name previously existed with that same UIDVALIDITY. Which means it either has to either trust that it's still the same folder after rename?
|
|
> >>
|
|
> >> I'm increasing UIDVALIDITY every time a new mailbox is created, so no two mailboxes have the same. This avoids conflicts with RENAME.
|
|
> >
|
|
> > We do this as well - but only within individual users, and mailboxes can be copied between users (yay shared mailboxes), so that would become prohibitively messy on a really large Cyrus instance.
|
|
>
|
|
> I don't allow RENAME across user boundaries. Seems potentially dangerous.
|
|
|
|
Legacy - gotta love it. You can't take things away from people...
|
|
|
|
That said, this is probably something that could be a config switch defaulting to "don't allow it unless the user is an admin" or something.
|
|
|
|
Bron.
|
|
|
|
--
|
|
Bron Gondwana
|
|
brong@fastmail.fm
|
|
|