Gnus development mailing list
 help / color / mirror / Atom feed
From: Nevin Kapur <nevin@jhu.edu>
Subject: Expiry and nnimap: ghost articles
Date: Tue, 25 Sep 2001 20:17:52 -0400	[thread overview]
Message-ID: <m3snda3ivj.fsf@fermat.mts.jhu.edu> (raw)

I recently switched to nnimap from nnml.

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: <m3hetr3qez.fsf@totally-fudged-out-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.

-- 
Nevin


             reply	other threads:[~2001-09-26  0:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26  0:17 Nevin Kapur [this message]
2001-09-26  7:31 ` Simon Josefsson
2001-09-26 16:56   ` Nevin Kapur
2001-09-26 17:56     ` Simon Josefsson
2001-09-26 21:10       ` Nevin Kapur
2001-09-27  8:43         ` Simon Josefsson
2001-09-27 14:41           ` Nevin Kapur
2001-09-27 15:54           ` Paul Jarc
2001-09-27 21:36             ` Simon Josefsson
2001-09-28 12:47               ` Kai Großjohann
2001-09-28 14:32               ` Nevin Kapur
2001-10-01 20:37               ` Paul Jarc
2001-10-02 17:50                 ` Simon Josefsson
2001-10-02 17:46               ` Paul Jarc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3snda3ivj.fsf@fermat.mts.jhu.edu \
    --to=nevin@jhu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).