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

37 lines
1.5 KiB
Plaintext

MBOX-Line: From jkt at flaska.net Fri Mar 7 08:01:49 2014
To: imap-protocol@u.washington.edu
From: =?iso-8859-1?Q?Jan_Kundr=E1t?= <jkt@flaska.net>
Date: Fri Jun 8 12:34:52 2018
Subject: [Imap-protocol]
=?iso-8859-1?q?Is_it_okay/common_for_servers_to_i?=
=?iso-8859-1?q?gnore_commands_sent_before_the_greeting=3F_=28gmail?=
=?iso-8859-1?q?_seems_to=3F=29?=
In-Reply-To: <5319E04C.3070105@mozilla.com>
References: <5319E04C.3070105@mozilla.com>
Message-ID: <cfe80347-ed90-4e5b-a69a-93f99e2158c4@flaska.net>
On Friday, 7 March 2014 16:05:48 CEST, Andrew Sutherland wrote:
> We're seeing a problem in the Firefox OS Gaia e-mail app where
> if we manage to send our "A1 CAPABILITY" request to the gmail
> IMAP server (initial-TLS imaps/993) before it sends its
> greeting, it acts like it never hears the request. Our
> not-so-clever state machine hangs until the connection times
> out.
Interesting. What my client is doing is patiently waiting for the initial
response and checking whether the capability list is passed in there as a
response code. The same for the tagged OK for the STARTTLS.
I am wondering whether you are deliberately trading bandwidth for latency,
and whether you have some measurements showing that sending the CAPABILITY
speculatively is beneficial. This is something which I haven't thought
about, and if you have already measured this, I would like to, er, "be
isnpired" :) and do it this way as well.
With kind regards,
Jan
--
Trojit?, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/