Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: nnimap move behaving like copy
Date: Fri, 11 Nov 2005 23:39:48 -0600	[thread overview]
Message-ID: <ubr0q4e6z.fsf@vignette.com> (raw)
In-Reply-To: <87br1336mr.fsf@phiwumbda.org>

"Jesse F. Hughes" <jesse@phiwumbda.org> writes:

> Hey ho.
>
> For some time now, whenever I move an article from one nnimap group to
> another (same server), it is failing to delete the article from the
> original group.  
>
> I've tried to diagnose the problem, but I don't know diddly about
> nnimap.  I've looked at nnimap-request-move-article.  The final
> command there is:
>
> 	     (imap-message-flags-add
> 	      (imap-range-to-message-set (list article))
> 	      "\\Deleted" 'silent nnimap-server-buffer)
>
> Gnus clearly reaches that command (I asked for messages before and
> after it).  But nonetheless, the article still sits happily on my
> server.
>
> I don't know how to figure out whether the article is being marked
> "Deleted" or not.  The server is a courier-imap server on another of
> my machines, so I have access to whatever logs are being created.
>
> The problem seems to have started after updating to No Gnus v0.3
> from Oort Gnus.  Any help would be greatly appreciated.

Do you have the agent enabled for this server?  If so, try turning it
off for a short test.  Open the group containing the original article
with the agent turned off.  Does the article still appear?  If so, can
you specify the precise command that you used?  The only time I use
nnimap is when I'm testing agent problems so I may not know how to
reproduce an obvious example.

Kevin


  reply	other threads:[~2005-11-12  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02  6:29 Jesse F. Hughes
2005-11-12  5:39 ` Kevin Greiner [this message]
2005-11-13  6:43   ` Kevin Greiner
2005-11-13  9:47     ` leon
2005-11-13 13:30       ` Sébastien Kirche
2005-11-14 21:40     ` Jesse F. Hughes

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=ubr0q4e6z.fsf@vignette.com \
    --to=kevin.greiner@vignette.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).