From mboxrd@z Thu Jan 1 00:00:00 1970 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_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17118 invoked from network); 12 Feb 2023 19:16:43 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 12 Feb 2023 19:16:43 -0000 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.94.2) (envelope-from ) id 1pRHq3-00AKXj-Tw for ml@inbox.vuxu.org; Sun, 12 Feb 2023 13:16:39 -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.96) (envelope-from ) id 1pRHq3-000F1n-2A for ml@inbox.vuxu.org; Sun, 12 Feb 2023 13:16:39 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1pRHpz-000F1g-1w for ding@lists.math.uh.edu; Sun, 12 Feb 2023 13:16:35 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pRHpw-0075ii-V2 for ding@lists.math.uh.edu; Sun, 12 Feb 2023 13:16:35 -0600 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=/o1t/cSovws1i9yNTHuigsegBnDZO7ezAGXvVpAPeb4=; b=kSm3Gfpp5kXP/ovbsvaFPqfyz+ eVuNEjTBIdTy6JL2dYg63DoVILeEEKNzoUbIs/ze9QJg6Sx7UfhpFMtA6f49dl+I5zjxzcpDh0z2u BtG/u1TdPC+DLZW8dSfmwLm01iibtTJ3KVjKIA2jSWEckwjoJmfDoyyFdNl9n74zk4Sg=; 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 1pRHpn-0001Ms-7q for ding@gnus.org; Sun, 12 Feb 2023 20:16:26 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pRHpk-0008NO-8X for ding@gnus.org; Sun, 12 Feb 2023 20:16:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: nnimap displays wrong article after server move Date: Sun, 12 Feb 2023 11:16:13 -0800 Message-ID: <87wn4mheyq.fsf@ericabrahamsen.net> References: <87lel5zecb.fsf@dod.no> <87h6vtzdlp.fsf@dod.no> <87o7q0xw4v.fsf_-_@dod.no> <87k00oxvpw.fsf@dod.no> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:2WK0Oxjw5XM4XiCaLcOA/Y300SY= List-ID: Precedence: bulk Steinar Bang writes: >>>>>> Steinar Bang : > >> Things to try: >> 1. Stop gnus and rename the agent directory for the server > > I did the following: > - I stopped gnus > - Renamed the ~/News/agent/nnimap/privat/ directory to ~/News/agent/nnimap/privat.old/ > - Started gnus > > Then gnus displayed the correct article. > > So it looks like gnus is using the agent to fetch the article for an > nnimap server, even with agent switched off for that server? If `gnus-agent-cache' is t, and data is present, Gnus will prefer the agent data for that server, even if it's no longer agentized. You'd have to shut the agent all the way off (`gnus-agent' -> nil) to ignore that data.