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.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 B065324F85 for ; Mon, 13 May 2024 16:40:37 +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 1s6Wqr-00000007og4-0oht for ml@inbox.vuxu.org; Mon, 13 May 2024 09:40:33 -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 1s6Wqr-00000004RkY-02CK for ml@inbox.vuxu.org; Mon, 13 May 2024 09:40:29 -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 1s6Wqo-00000004RkP-0Z53 for ding@lists.math.uh.edu; Mon, 13 May 2024 09:40:26 -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 1s6Wqe-00000007of1-1GQx for ding@lists.math.uh.edu; Mon, 13 May 2024 09:40:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=OIOoMzb8376yaXLGGkXxzPDfCpSh3NE21Xi9m2owhbQ=; b=lAdYuiCerCaezTLvhoeP5psrYa FtevfIyJu3V9lutNL4HKKBlxshkAMziir8tI+sCijUcQ6vJWDWHCgNvNBAD7GzPllNQferXEYM+jK izuPItp/Sloc/oRIfn4HFFg4k4p8VZmuZ4t5u4ToJEWvic1AZNHuP0ZZVNKpU1jHiWcI=; 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 1s6WqN-0002b0-6p for ding@gnus.org; Mon, 13 May 2024 16:40:01 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1s6WqL-000711-4M for ding@gnus.org; Mon, 13 May 2024 16:39:57 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: Gnus sometimes fails to see a message that is actually in IMAP Date: Mon, 13 May 2024 07:39:47 -0700 Message-ID: <87a5ktai8c.fsf@ericabrahamsen.net> 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> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:LSii3ZrYcrRMjod4T1i8Cr0Crw0= List-ID: Precedence: bulk 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. > > > Eric Abrahamsen writes: > >> I was going to say, the IMAP implementation of Outlook is indeed bad! >> But that's "good" that you're hitting this issue with Dovecot running >> locally, as that's a setup with fewer confounding variables, and also >> what I run, so maybe we stand a better chance of reproducing. > > Yes, it does seem more tractable. > > One thing I find troublesome about modern gnus is that it is part of > emacs. I'm currently running 28.2, so that's the gnus I have. Years > before, when gnus was in a separate repo, I was running up-to-date gnus > with stable emacs. If I'm confused and we should be debugging gnus > trunk please let me know. Not confused, of course, but I do think that Emacs 28 is a little bit too old for this sort of debugging. Ideally we'd be doing it on master, though 29 is still worthwhile, if you can update to that. There are good things in the past couple of versions. [...] > It would also be interesting to have a gnus-imap-revalidate function that > for all cached information, fetches it and compares, complaining loudly > if different. I have used this technique when debugging routing code to > end up with only correct cached information, and didn't think of any > other way to find rare bugs. This is a really good idea. There's been talk on this list of forcibly resetting Gnus to the remote server's state at start-up, which would be something of a band-aid, but this would stand us a better chance of pinning down the bug. People could run it at Gnus startup and shutdown, as well as on-demand. I'll look into putting this together.