From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/38936 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: Expiry and nnimap: ghost articles Date: Wed, 26 Sep 2001 09:31:17 +0200 (CEST) Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035174724 25207 80.91.224.250 (21 Oct 2002 04:32:04 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:32:04 +0000 (UTC) Cc: Return-Path: Return-Path: Original-Received: (qmail 25651 invoked from network); 26 Sep 2001 07:22:27 -0000 Original-Received: from lie.extundo.com (195.42.214.244) by gnus.org with SMTP; 26 Sep 2001 07:22:27 -0000 Original-Received: from localhost (jas@localhost) by lie.extundo.com (8.11.6/8.11.6) with ESMTP id f8Q7VHo23707; Wed, 26 Sep 2001 09:31:18 +0200 X-Authentication-Warning: lie.extundo.com: jas owned process doing -bs Original-To: Nevin Kapur In-Reply-To: Original-Lines: 30 Xref: main.gmane.org gmane.emacs.gnus.general:38936 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:38936 On Tue, 25 Sep 2001, Nevin Kapur wrote: > I have a custom expiry-target that decides where a message lands up > after it has expired. I have not changed this function since I > switched to nnimap and the behavior I describe is nnimap-specific. > > Each time expiry happens and an article gets moved to one of my > nnfolder archive groups, some ghost messages appear in that group. > Here is the *Summary* buffer from one of them. > > 12/31/99 [nobody ] (none) > Sep 15 [-> xxx xxxxxx ] xxx@xx36216-x.xxxx1.xx.xxxx.xxx xxxx xxx xxxx > > The ghost article looks like this with C-u g: > > ,---- > | X-From-Line: nobody Tue Sep 25 17:35:00 2001 > | Message-ID: > | Lines: 0 > | Xref: fermat.mts.jhu.edu Archive-2001-Sep:619 > | X-Gnus-Article-Number: 619 Tue Sep 25 17:35:00 2001 > `---- > > This behavior is repeatable. It also occurs when I move an > article from one imap group to another. Frob `imap-log' and send the contents from the imap log buffer after moving one article and entering the destination group and doing C-u g on the article. Thanks.