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

32 lines
1.3 KiB
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Thu Mar 20 12:30:09 2014
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun 8 12:34:52 2018
Subject: [Imap-protocol] Detecting HIGHESTMODSEQ changes/polling for
flag changes
In-Reply-To: <38fb5091-dd83-484e-9b95-49ed42899485@flaska.net>
References: <4E9EBB0E-ADFB-4F79-A27B-51ADC8395D71@apple.com>
<38fb5091-dd83-484e-9b95-49ed42899485@flaska.net>
Message-ID: <fd7beba7-dd03-4cb7-b370-fc934c32e908@gulbrandsen.priv.no>
On Thursday, March 20, 2014 8:07:29 PM CEST, Jan Kundr?t wrote:
> The fact is that compared to the API which is available to
> their own client, the interface made available via IMAP is
> seriously limited. Take your own conclusions from that.
Slack must be cut ;)
Their own client is maintained by people who have lunch with the server
developers every other day. You're a client developer, but you don't have
lunch with the server people.
Brandon will tell you that he wants to treat you exactly as well as he
treats their own client developers, and I think he honestly does want to do
that. I even think their official policy matches Brandon's opinion, if they
have an official policy. But you don't eat lunch with Brandon's team, and
having lunch beats both official policies and preferences.
Arnt