115 lines
3.4 KiB
Plaintext
115 lines
3.4 KiB
Plaintext
MBOX-Line: From brong at fastmail.fm Sat Feb 18 14:44:11 2017
|
|
To: imap-protocol@u.washington.edu
|
|
From: Bron Gondwana <brong@fastmail.fm>
|
|
Date: Fri Jun 8 12:34:55 2018
|
|
Subject: [Imap-protocol] Is SELECT required before FETCH to detect new
|
|
mail?
|
|
In-Reply-To: <CABa8R6tSevQ7kda5usVW-DuKO68Kdukgf7USZ=eTCWpvY-Nobw@mail.gmail.com>
|
|
References: <bb8d0ae1-dda0-dbce-186a-2a668946ec7b@chartertn.net>
|
|
<CABa8R6tLdckvJ9c-UHHijbvJ95fBGBN41fxhypO1yWzt0tGOMQ@mail.gmail.com>
|
|
<3e01f804-163d-cda3-f5bb-b495fa5a1d50@chartertn.net>
|
|
<CABa8R6tSevQ7kda5usVW-DuKO68Kdukgf7USZ=eTCWpvY-Nobw@mail.gmail.com>
|
|
Message-ID: <1487457851.3495664.885450568.157A4E2A@webmail.messagingengine.com>
|
|
|
|
Surely a noop should work to cause an update?
|
|
|
|
|
|
|
|
|
|
|
|
On Sun, 19 Feb 2017, at 09:36, Brandon Long wrote:
|
|
|
|
> You shouldn't have to reselect, and doing so is really inefficient on
|
|
> some servers, so I wouldn't recommend it as the default mechanism.
|
|
>
|
|
|
|
> Seems like for this server there is no benefit to keeping the
|
|
> connection open.
|
|
>
|
|
|
|
> I would consider a modern server which does this as pretty broken, but
|
|
> it may not violate the spec.
|
|
>
|
|
|
|
> On Feb 18, 2017 2:29 PM, "Gene Smith" <gds@chartertn.net> wrote:
|
|
|
|
>> The charter IMAP server is openwave according the login response. So
|
|
>> are you saying it is OK for the IMAP server to require a new SELECT
|
|
>> before doing a FETCH on an already selected mailbox for the FETCH
|
|
>> response to indicate new email? If so, this is a bug in thunderbird.
|
|
>>
|
|
|
|
>> I have noticed that at least one client (kmail) always does SELECT
|
|
>> and FETCH when checking for new mail (even when inbox is already
|
|
>> selected). However, thunderbird and claws-mail only do a FETCH and
|
|
>> don't re-do the SELECT and, therefore, don't detect new mail unless
|
|
>> another folder is looked at first and then inbox is returned to.
|
|
>>
|
|
|
|
>> -gene
|
|
|
|
>>
|
|
|
|
>> On 02/18/2017 05:00 PM, Brandon Long wrote:
|
|
|
|
>>> Didn't the old UW IMAP server act that way with certain mailbox
|
|
>>> formats? It locked the mailbox and it couldn't receive new mail.
|
|
>>>
|
|
|
|
>>> In any case, I don't think the spec precludes implementing it that
|
|
>>> way, but it's certainly not the normal implemention.
|
|
>>>
|
|
|
|
>>> Brandon
|
|
|
|
>>>
|
|
|
|
>>> On Feb 18, 2017 1:52 PM, "Gene Smith" <gds@chartertn.net> wrote:
|
|
|
|
>>>
|
|
|
|
>>>> I have been seeing a problem with mozilla Thunderbird client when
|
|
>>>> using the charter.net imap server. When thunderbird checks for new
|
|
>>>> messages it just does a FETCH since the inbox was already SELECTed
|
|
>>>> at startup. It does not detect new messages unless another mailbox
|
|
>>>> is SELECTed and inbox is re-SELECTED and then FETCHed. I think
|
|
>>>> thunderbird is following the IMAP spec but charter.net server is
|
|
>>>> not since it requires a re-SELECT on and already selected mailbox
|
|
>>>> to signal new email. Am I right?
|
|
>>>>
|
|
|
|
>>>> -gene
|
|
|
|
>>>> _______________________________________________
|
|
|
|
>>>> Imap-protocol mailing list
|
|
|
|
>>>> Imap-protocol@u.washington.edu
|
|
|
|
>>>> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
|
|
|
|
>>
|
|
|
|
|
|
|
|
> _________________________________________________
|
|
|
|
> Imap-protocol mailing list
|
|
|
|
> Imap-protocol@u.washington.edu
|
|
|
|
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
|
|
|
|
|
|
|
|
--
|
|
|
|
Bron Gondwana
|
|
|
|
brong@fastmail.fm
|
|
|
|
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20170219/fac5e25f/attachment.html>
|