From: "Jakub Ječmínek" <kuba@kubajecminek.cz>
To: ding@gnus.org
Subject: Re: ProtonMail Bridge Patch
Date: Sun, 18 Feb 2024 17:57:28 +0000 [thread overview]
Message-ID: <87r0h94pvh.fsf@kubajecminek.cz> (raw)
In-Reply-To: <87y1bhpt1o.fsf@ericabrahamsen.net>
"Eric Abrahamsen" <eric@ericabrahamsen.net> writes:
>> I might be wrong of course but I think that the latter and that there's
>> good chance sorting the headers would fix this issue.
>
> I still haven't found anything that looks like a hard requirement that
> headers be sorted, but that doesn't mean it isn't there.
That was only my guess (based on very shallow understanding of the Gnus
internals). I can try to implement sorting and see if that helps. This
is what I found inside Gnus manual but I'm not sure if that's relevant
for this issue:
[...] article numbers must be assigned in order of arrival in the group;
this is not necessarily the same as the date of the message.
> 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.
--
Kuba Ječmínek (http://kubajecminek.cz)
next prev parent reply other threads:[~2024-02-18 17:58 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 [this message]
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
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=87r0h94pvh.fsf@kubajecminek.cz \
--to=kuba@kubajecminek.cz \
--cc=ding@gnus.org \
/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).