Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Problem when respooling with nnimap
Date: 21 Jun 2005 15:10:56 -0400	[thread overview]
Message-ID: <4nd5qfo79b.fsf@lifelogs.com> (raw)
In-Reply-To: <plop87aclkbwq9.fsf@gnu-rox.org> (Xavier Maillard's message of "Mon, 20 Jun 2005 22:26:52 +0200")

On Mon, 20 Jun 2005, zedek@gnu-rox.org wrote:

> Hello,
> 
> I have a problem when trying to respool messsages held by a
> nnimap backend.
> 
> Here is a backtrace:
> 
> ,----
>| Debugger entered--Lisp error: (error "Process imap not running")
>|   process-send-string(#<process imap> "285 APPEND \".\n")
>|   imap-send-command-1("285 APPEND \"")
>|   imap-send-command(("APPEND \"" nil "\" " #<buffer *copy article*>) nil)
>|   imap-send-command-wait(("APPEND \"" nil "\" " #<buffer  *copy article*>))
>|   imap-message-append(nil #<buffer  *copy article*> nil nil " *nnimap* gnu-rox.org")
>|   nnimap-request-accept-article(nil "gnu-rox.org" nil)
>|   gnus-request-accept-article(nil (nnimap "gnu-rox.org") nil t)
>|   gnus-summary-move-article(nil nil (nnimap "gnu-rox.org") copy)
>|   gnus-summary-copy-article(nil nil (nnimap "gnu-rox.org"))
>|   gnus-summary-respool-article(nil (nnimap "gnu-rox.org"))
>|   call-interactively(gnus-summary-respool-article)
> `----
> 
> Here is what it shows on my \*Message\* buffer:
> 
> ,----
>| Registry: article <874qddwrs3.fsf@dod.no> spooled to
>| 	nnimap+gnu-rox.org:INBOX.ml.emacs.ding
>| Error in IMAP command received by server.
>| Couldn't Copy article 1: Error in IMAP command received by server.
>| Registry: article <87sm0t1l68.fsf@ashbery.wjsullivan.net> spooled to nnimap+gnu-rox.org:INBOX.ml.emacs.ding
>| Error in IMAP command received by server.
>| Couldn't Copy article 43: Error in IMAP command received by server.
>| Registry: article <87sm0xzi6b.fsf@rocksteady.printf.se> spooled to nnimap+gnu-rox.org:INBOX.ml.emacs.ding
> `----
> 
> (repeated many times)
> 
> What is going on ?

From the errors, it looks like the IMAP server is either disconnected
or nnimap.el lost track of it.  Simon will probably look at this, but
you should provide more information:

You should tell us the name and version of the IMAP server.

Also set imap-debug or nnimap-debug (I forget which one is right) to
get a full log of the IMAP commands exchanged between Gnus and the
problematic IMAP server.  That is essential to debugging IMAP problems.

Ted



  parent reply	other threads:[~2005-06-21 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 20:26 Xavier Maillard
2005-06-21 17:00 ` Xavier Maillard
2005-06-21 19:10 ` Ted Zlatanov [this message]
2009-11-20 23:11   ` Sebastian P. Luque

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=4nd5qfo79b.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).