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=-2.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL 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 A6F9628D39 for ; Fri, 24 May 2024 19:30:15 +0200 (CEST) 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 1sAYk5-00000002y8m-0Vyi for ml@inbox.vuxu.org; Fri, 24 May 2024 12:30:13 -0500 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 1sAYk4-00000004mkA-3piI for ml@inbox.vuxu.org; Fri, 24 May 2024 12:30:08 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1sAYjw-00000004mjt-3xIS for ding@lists.math.uh.edu; Fri, 24 May 2024 12:30:06 -0500 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 1sAYjv-00000002y80-357q for ding@lists.math.uh.edu; Fri, 24 May 2024 12:30:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=qRAFswoFntnE5GyWly8tRmrmSi6ij85WTh/IYcVcjE8=; b=tddaN+3I8WHuzYfHRiCOhsvmmW 0yEVpfQahdz/h0Nh7WuQsrHkGjwYYepxtBecfu5HAjq24fruB6w/SgFR5+yn1HVghiGKoblLDhMDD +11nIcdanm61n5FFBsqSWP29JsJ2HDkGHS6xSMZ00K1EOluX38nh5c3fHNCCahOmMARs=; Received: from mail.ericabrahamsen.net ([52.70.2.18]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sAYjj-0007zl-QL for ding@gnus.org; Fri, 24 May 2024 19:29:50 +0200 Received: from localhost (71-212-21-65.tukw.qwest.net [71.212.21.65]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 9BC9CFA39F; Fri, 24 May 2024 17:29:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1716571785; bh=qRAFswoFntnE5GyWly8tRmrmSi6ij85WTh/IYcVcjE8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Tu8S/XRmBt7y4tO706/Yyq7o4z8SnS6SUYKW1tM7ww+4XDn5wntMaSiuVZ6Gtn8vX Hel0c4vQVzr5xirPIn9rzAu2UnURb4p7et4bT+Ba/Lu2uOdllyT9B9jzREN1M6n33/ XZ8ERge3C2RI8EY9L3wt7BfucIsqVQ91NaN7gdIw= From: Eric Abrahamsen To: ding@gnus.org Cc: Greg Troxel , Andrew Cohen Subject: Re: Gnus sometimes fails to see a message that is actually in IMAP In-Reply-To: <87r0dr6w27.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 24 May 2024 08:58:40 -0700") References: <87h6g7mm8r.fsf@debian-hx90.lan> <878r1blqcg.fsf@uwo.ca> <87ttjx55ey.fsf@uwo.ca> <875xwalmf4.fsf@ericabrahamsen.net> <87wmoqjf92.fsf@ericabrahamsen.net> <874jbmk2ql.fsf@debian-hx90.lan> <87msoyfoo4.fsf@debian-hx90.lan> <87plttctyy.fsf@debian-hx90.lan> <87msow9dwx.fsf@ericabrahamsen.net> <87a5ktai8c.fsf@ericabrahamsen.net> <87r0dr6w27.fsf@ericabrahamsen.net> Date: Fri, 24 May 2024 10:29:43 -0700 Message-ID: <87le3z6rug.fsf@ericabrahamsen.net> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain List-ID: Precedence: bulk Eric Abrahamsen writes: > Eric Abrahamsen writes: > >> Greg Troxel writes: >> >> Wow, this is a ton of information! Thanks for all the background. Kudos >> on using TLS on your own machine, something I have never had the >> patience to set up. >> >>> I have changed the subject, as I am not at all sure that my problem is >>> the same as "reports new messages but not showing them on IMAP server". >>> In my case, it seems to me as if there is a filter between gnus and the >>> IMAP server that redacts a message. > > Brief update -- when I started looking further into this, I realized > that I have the same issue with the INBOX of one of my main IMAP > accounts. I'd just not noticed because I have 486 unread messages in > that folder :( Well, 483 according to Gnus. > > This account includes a remote Dovecot on the server that actually > receives mail, and two local machines that each have their own local > Dovecot, and Emacs/Gnus. The remote and local Dovecots are synced with > mbsync, and both remote and local report 486 unread messages when > checked with doveadm. > > My other local machine is currently not booting, but I'll be very > curious to see if Gnus on that machine is wrong in the same way > (a deterministic bug) or not (space gremlins). > > Otherwise, the difference between "g" and "M-g", for IMAP servers that > support qresync, is that "g" goes the qresync route: > > EXAMINE (QRESYNC ( )) > > while "M-g" does a full fetch of flags: > > "UID FETCH 1:* FLAGS" > > So that's a pretty strong indicator that there's a bug in the qresync > branch of `nnimap-update-qresync-info'. Some have reported bugs that > *weren't* resolved by "M-g", so there will likely be a few things to > fix, but one thing at a time. I'm currently looking with deep suspicion at the very beginning of that function: ;; Add all the vanished articles to the list of read articles. (setf (gnus-info-read info) (range-add-list (range-add-list (range-concat (gnus-info-read info) vanished) (cdr (assq '%Flagged flags))) (cdr (assq '%Seen flags))))