Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Expiry and nnimap: ghost articles
Date: Thu, 27 Sep 2001 23:36:26 +0200	[thread overview]
Message-ID: <ilud74c5nad.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m3hetoy6h1.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Thu, 27 Sep 2001 11:54:12 -0400")

prj@po.cwru.edu (Paul Jarc) writes:

> Simon Josefsson <jas@extundo.com> wrote:
> > Yes, since nnimap doesn't support `nnchoke-request-move-article' (it is
>> impossible to implement in IMAP) Gnus does retrieve+delete instead, and
>> the delete code move things into the expiry-target.
>
> Couldn't nnimap just do the retrieve+delete within
> -request-move-article?

Um, yes, now that I look at it, this is how it is done. :-) I was
thinking of `nnchoke-request-replace-article'...

Then I wonder why this happens.  Ah, yes -- if you move an article
from a nnimap group to a nnfolder group (which was the case in this
thread), moving doesn't happen within one backend, so Gnus does
retrieve+delete.  And nnimap can't know this case from the case where
articles are simply expired.  Neither could nnml or nnfolder, so I
guess this is a generic problem.




  reply	other threads:[~2001-09-27 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26  0:17 Nevin Kapur
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 [this message]
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=ilud74c5nad.fsf@barbar.josefsson.org \
    --to=jas@extundo.com \
    /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).