From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: "Jakub Ječmínek" <kuba@kubajecminek.cz>, ding@gnus.org
Subject: Re: ProtonMail Bridge Patch
Date: Mon, 19 Feb 2024 13:40:36 -0800 [thread overview]
Message-ID: <871q98m8tn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sf1o71pd.fsf@miraculix.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork"'s message of "Mon, 19 Feb 2024 19:23:26 +0100")
Bjørn Mork <bjorn@mork.no> writes:
> Jakub Ječmínek <kuba@kubajecminek.cz> writes:
>> "Eric Abrahamsen" <eric@ericabrahamsen.net> writes:
>>
>>> I also wasn't able to find anything explicit in RFC 3501 or 9051 about
>>> the order of FETCH responses -- for my information, can you point me in
>>> the right direction?
>>
>> That's the thing. There's nothing explicit in RFC 3501 about the message
>> order so AFAIK the consensus is that UIDs don't have to be sorted.
>
> I was curiuos about this too and went looking. I believe the definition
> of "sequence-set" (which is what the ID range in the FETCH request is)
> on https://datatracker.ietf.org/doc/html/rfc3501#page-90 suggests that
> clients should expect replies in any order:
>
> Servers MAY coalesce overlaps and/or execute the sequence in any
> order.
Thanks! I hadn't looked as far as the formal syntax section, that's helpful.
prev parent reply other threads:[~2024-02-19 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 17:29 Jakub Ječmínek
2024-02-17 18:05 ` Eric Abrahamsen
2024-02-17 18:44 ` Jakub Ječmínek
2024-02-18 17:43 ` Eric Abrahamsen
2024-02-18 17:57 ` Jakub Ječmínek
2024-02-18 18:30 ` Eric Abrahamsen
2024-02-20 11:59 ` Jakub Ječmínek
2024-02-22 17:18 ` Eric Abrahamsen
2024-02-22 22:46 ` Jakub Ječmínek
2024-02-23 2:23 ` Eric Abrahamsen
2024-02-23 11:57 ` Jakub Ječmínek
2024-02-19 18:23 ` Bjørn Mork
2024-02-19 21:40 ` Eric Abrahamsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q98m8tn.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=bjorn@mork.no \
--cc=ding@gnus.org \
--cc=kuba@kubajecminek.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).