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.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_DOTEDU_SUSP, 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 97C6B28EC0 for ; Sat, 17 Feb 2024 18:30:00 +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 1rbOVj-0000000EjkF-1AXW for ml@inbox.vuxu.org; Sat, 17 Feb 2024 11:29:59 -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 1rbOVj-00000000cXX-08W4 for ml@inbox.vuxu.org; Sat, 17 Feb 2024 11:29:59 -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 1rbOVf-00000000cXO-1GNi for ding@lists.math.uh.edu; Sat, 17 Feb 2024 11:29:56 -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 1rbOVd-0000000Ejjg-1PjH for ding@lists.math.uh.edu; Sat, 17 Feb 2024 11:29:55 -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:Message-ID :Subject:From:To:Date:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=NEw+ge3o6xuWKcjUAYXNb372Ehz12AvyjPqOFGPxNek=; b=EHFkaSoRh1E7yP+EsysOudC39u /4YoyCW5F771o7kgQ2QqvwmzOZT5dSsb4GW+cjJs9Gjp9V9vcXLZwsKvT1jv5gDYKxjmNglal7vrc EXwI3XIQ88Z3vLabq3vreqHfs6H4JWr85KWDzgG/uclpEerlxE/6vgTwMCRw3jVXXhoU=; Received: from mail-4323.proton.ch ([185.70.43.23]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rbOVV-0004gu-Aq for ding@gnus.org; Sat, 17 Feb 2024 18:29:48 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kubajecminek.cz; s=protonmail; t=1708190982; x=1708450182; bh=NEw+ge3o6xuWKcjUAYXNb372Ehz12AvyjPqOFGPxNek=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=NWkLiq18miaN0BT0HUzZQz+QeVTHrOXP06W1Ql7g0uPGNJi8wH7TTfxkh1UMORbwk TdDoQpHTxOnHGFoLKLJrM/bz/TyVT0qqCg8wFelicbrJTsr9A4/9XR8py7kfSPjvPH sJYdbkBvFiRmK5Zqo4Vg8588w6wMF/xhk6nT/ZFH8Ki0gobsPxlCgXONzy2m6pNSVS RYzh3ctrTjaZ+wDgNJ+h1vQ83LVYiRUbr6HaFPn9YDATB+NqR79a4Q3E8tKg8xXwEf 7v7MPz0NYiGoK4ncMukqSG/5iU09L96r1kQwNmaGoYZcuGcM3DyLAWtIk508aaD/0r jvn9DYsvAobXA== Date: Sat, 17 Feb 2024 17:29:24 +0000 To: ding@gnus.org From: =?utf-8?Q?Jakub_Je=C4=8Dm=C3=ADnek?= Subject: ProtonMail Bridge Patch Message-ID: <86msrzknim.fsf@kubajecminek.cz> Feedback-ID: 98803324:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: Precedence: bulk Hello, I'm not sure if this is the correct place to post this but I wish there was this information somewhere like a week ago. I recently switched my mail provider to ProtonMail which lets you use IMAP/SMTP protocol only if you run something called ProtonMail Bridge on your machine. This software basically acts as a local IMAP/SMTP server and communicates with the upstream servers in a secured fashion (or at least this is the rationale). The problem is that Gnus and Gluon - IMAP server embedded inside ProtonMail Bridge - doesn't work well together. Gnus (nnimap back end) was acting like a lunatic and it took me a while before I found the real reason for its behaviour. Gnus expects that the messages are returned from a FETCH request in a ascending (predictable?) order but Gluon responds each time differently. Example communication might look like this: Gnus: FETCH 1:3 ... Gluon: * 3 RESPONSE ... Gluon: * 1 RESPONSE ... Gluon: * 2 RESPONSE ... This is apparently a valid response according to RFC 3501. But luckily for us there's server option inside Gluon which let's you disable parallelism and ultimately fix message shuffling. Here's the patch for proton-bridge package: >From 23f9c69a1552af1f946687f55de901488a2c9a38 Mon Sep 17 00:00:00 2001 From: =3D?UTF-8?q?Jakub=3D20Je=3DC4=3D8Dm=3DC3=3DADnek?=3D Date: Fri, 16 Feb 2024 16:07:21 +0100 Subject: [PATCH] Gnus Fix: disable parallelism --- internal/services/imapsmtpserver/imap.go | 1 + 1 file changed, 1 insertion(+) diff --git a/internal/services/imapsmtpserver/imap.go b/internal/services/i= mapsmtpserver/imap.go index 63888b51..358173c6 100644 --- a/internal/services/imapsmtpserver/imap.go +++ b/internal/services/imapsmtpserver/imap.go @@ -120,6 +120,7 @@ func newIMAPServer( =09=09gluon.WithReporter(reporter), =09=09gluon.WithUIDValidityGenerator(uidValidityGenerator), =09=09gluon.WithPanicHandler(panicHandler), +=09=09gluon.WithDisableParallelism(), =09) =09if err !=3D nil { =09=09return nil, err --=20 2.42.0 --=20 Kuba Je=C4=8Dm=C3=ADnek