From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from mx1.math.uh.edu (mx1.math.uh.edu [129.7.128.32]) by inbox.vuxu.org (Postfix) with ESMTP id 20D592862B for ; Sun, 18 Feb 2024 18:43:52 +0100 (CET) Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rblCf-0000000FNKk-3OXF for ml@inbox.vuxu.org; Sun, 18 Feb 2024 11:43:49 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.97.1) (envelope-from ) id 1rblCZ-00000000ek7-1Piq for ml@inbox.vuxu.org; Sun, 18 Feb 2024 11:43:43 -0600 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1rblCR-00000000ejy-1Uum for ding@lists.math.uh.edu; Sun, 18 Feb 2024 11:43:40 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rblCQ-0000000FNKK-1VID for ding@lists.math.uh.edu; Sun, 18 Feb 2024 11:43:35 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References :Message-ID:Date:Subject:From:To:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=paJeQxgUkoZY5xQ7/++f53j3Gie2EzcRnth28+xGJbw=; b=Fak6gsZim6BTMVBwICKvUbdM6n +Qu851oRSgq48M0YMjQFrXjP+RRbnX+UmtG2x1ayR7+TYJZK9M6Uf0ICX4mp1F6ipVo1rmfW8ngKi 9ihn0T12+Y/ywgoi5VU7JDqwVUyB+K2NqB6YlLrgaNjLx/swP0wr/Zid1BkBeUHGVMrQ=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rblCJ-00088b-CC for ding@gnus.org; Sun, 18 Feb 2024 18:43:29 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1rblCH-000AGX-Pt for ding@gnus.org; Sun, 18 Feb 2024 18:43:25 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: ProtonMail Bridge Patch Date: Sun, 18 Feb 2024 09:43:15 -0800 Message-ID: <87y1bhpt1o.fsf@ericabrahamsen.net> References: <86msrzknim.fsf@kubajecminek.cz> <87frxrq84g.fsf@ericabrahamsen.net> <86cysvexqv.fsf@kubajecminek.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:k7vlExH0SleYNClWF3UCKfzE+BE= List-ID: Precedence: bulk Jakub Ječmínek writes: > "Eric Abrahamsen" writes: > >> Thanks a lot for this note! I'm glad you found a solution, but if >> out-of-order FETCH UIDs are valid according to the RFC, Gnus should also >> handle that. >> >> I assume the problem is in `nnimap-transform-headers'? Nothing in there >> jumps out at me immediately. Or maybe the problem is that the function >> doesn't sort the parsed headers, and Gnus' next step expects the headers >> to be in sorted order? > > 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. 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? Thanks, Eric