From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/52999 Path: main.gmane.org!not-for-mail From: Kevin Greiner Newsgroups: gmane.emacs.gnus.general Subject: Re: Agent: delete agentized message? Date: Wed, 04 Jun 2003 00:51:18 -0500 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <84smqreey0.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1054705848 29726 80.91.224.249 (4 Jun 2003 05:50:48 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 4 Jun 2003 05:50:48 +0000 (UTC) Original-X-From: ding-owner+M1543@lists.math.uh.edu Wed Jun 04 07:50:47 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19NRAF-0007iT-00 for ; Wed, 04 Jun 2003 07:50:23 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19NRBs-00024u-00; Wed, 04 Jun 2003 00:52:04 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19NRBW-00024o-00 for ding@lists.math.uh.edu; Wed, 04 Jun 2003 00:51:42 -0500 Original-Received: (qmail 5444 invoked by alias); 4 Jun 2003 05:51:41 -0000 Original-Received: (qmail 5439 invoked from network); 4 Jun 2003 05:51:41 -0000 Original-Received: from quimby.gnus.org (80.91.224.244) by sclp3.sclp.com with SMTP; 4 Jun 2003 05:51:41 -0000 Original-Received: from news by quimby.gnus.org with local (Exim 3.12 #1 (Debian)) id 19NRQd-00077A-00 for ; Wed, 04 Jun 2003 08:07:19 +0200 Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-Lines: 49 Original-NNTP-Posting-Host: manchester-suites-iaf1047853.cust-rtr.ameritech.net Original-X-Trace: quimby.gnus.org 1054706839 27351 68.23.64.46 (4 Jun 2003 06:07:19 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 4 Jun 2003 06:07:19 GMT User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:TP727NOr8soVfDCgnJ6SeC2m/FA= Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:52999 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:52999 kai.grossjohann@gmx.net (Kai Großjohann) writes: > My boss has his nnimap:INBOX under agent control. There are some > very old articles known to the agent, but they are not on the server > anymore. Hitting `B DEL' on them says `cannot delete article 1054'. > > Is it normal for Gnus to behave like that? It would seem that the behavior is entirely up to the backend. The command 'B DEL' is bound to gnus-summary-delete-article. It then calls gnus-request-expire-articles to perform the actual work. g-r-e-a passes the request to the request-expire-articles method of the backend. That method performs the request then returns a list of articles that could not be deleted by the backend. Finally, that list is used by g-r-e-a to compute the articles that should be removed from the agent. >From your description, the backend is apparently failing to distinguish between an error caused by an article that is no longer on the server and an error caused by, for example, being unable to connect to the server. > I did M-x gnus-agent-regenerate-group RET, but that didn't help. (It > did move all those old articles from ancient status to unread status, > though.) How did you respond to the 'Reread?' prompt? If you evaluate (gnus-agent-regenerate-group "group.name" t), you'll get the behavior that you just described. On the other hand, if you evaluate (gnus-agent-regenerate-group "group.name"), you should NOT see any change in an article's status. > I then marked some of the old spam as expirable and did M-x > gnus-agent-expire-group RET. That did the job. Good. > WIBNI the Agent would delete its copy of a message when people do B > DEL on an article that isn't on the server? Well, it would seem that that decision is controlled by the backend. I took a look at nnimap-request-expire-articles and I'm not going to be able to take this much further. Someone comfortable with the nnimap backend will need to see if the 'cannot delete article BECAUSE IT DOESN'T EXIST ON THE SERVER' error can be handled differently than every other error. Kevin