From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: Moving articles with IMAP
Date: 07 Nov 1999 23:08:22 +0100 [thread overview]
Message-ID: <iluwvrurm3t.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Denys Duchier's message of "07 Nov 1999 22:26:48 +0100"
Denys Duchier <Denys.Duchier@ps.uni-sb.de> writes:
> Here I am again, going bump in the night.
Thanks for still being with us. :-)
> I just tried moving a message from one IMAP folder to another using
> `B m'. This didn't work. I got a message that said that the
> message (identified by number) could not be moved.
What was the exact error message? Did it contain a reason? Nnimap
uses `nnheader-report' to report IMAP server errors.
> Then a new bogus server was created for the group into which I had
> tried to move the message, and that group could no longer be
> selected.
I think it's best to solve this bogus server problem first, it might
be the cause of the other problems you're having.
> I got an error message that said "this should not happen". That
> sounds like the imap dwarf that dwells in gnus is being very unhappy
> about his circumstances. What's bugging the little guy?
I've fixed it in pGnus CVS (changelog below). I think the check
whether the error should be signaled or not was wrong.
> Also, why is it that I have these large and ever increasing buffers
> called *nnimap-debug* and *imap-log*?
Debug stuff, I've disabled it. When trying to debug the article move
problem, it might be a good idea to set `imap-log' to "*imap-log*" (or
something) to re-enable it.
1999-11-07 Simon Josefsson <jas@pdc.kth.se>
* nnimap.el (nnimap-open-server): Remove error signal if
nnimap-server-buffer is nil (the check should've been `boundp').
* imap.el (imap-log):
* nnimap.el (nnimap-debug): Disable debugging by default.
prev parent reply other threads:[~1999-11-07 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-07 21:26 Denys Duchier
1999-11-07 22:08 ` Simon Josefsson [this message]
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=iluwvrurm3t.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--cc=ding@gnus.org \
/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).