From: Arcady Genkin <antipode@thpoon.com>
Subject: Deleting an article on IMAP server
Date: 03 Sep 2000 03:56:35 -0400 [thread overview]
Message-ID: <87pumlhpsc.fsf@tea.thpoon.com> (raw)
I have to go through this at least once every day. I open an article
in an nnimap group, then leave it open and switch to doing something
else for a while. Then when I come back, and try to delete the
article, I get an error (the following backtrace):
Signaling: (error "Process not open for writing" #<network connection "imap" (143 . "soup") state:exit>)
process-send-string(#<network connection "imap" (143 . "soup") state:exit> "4089 UID STORE 972 +FLAGS (\\Deleted)\r\n")
imap-send-command-1("4089 UID STORE 972 +FLAGS (\\Deleted)")
imap-send-command("UID STORE 972 +FLAGS (\\Deleted)" nil)
imap-send-command-wait("UID STORE 972 +FLAGS (\\Deleted)")
imap-message-flags-add("972" "\\Deleted")
nnimap-request-expire-articles((972) "mail/private" "soup" force)
gnus-request-expire-articles((972) "nnimap+soup:mail/private" force)
gnus-summary-delete-article(nil)
call-interactively(gnus-summary-delete-article)
I guess the connection to the IMAP server expires, but that's just a
guess. I have to tick the message, leave the group, re-enter it, and
delete the message. This raises two questions:
1. Is this a bug or limitation of IMAP protocol/backend?
2. Is there a way to work around this without doing the
tick-exit-enter-delete sequence?
I'm using Gnus 5.8.7 under Xemacs 21.1.11 and UofW IMAP server.
Thanks!
--
Arcady Genkin
Don't read everything you believe.
next reply other threads:[~2000-09-03 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-03 7:56 Arcady Genkin [this message]
2000-09-03 14:13 ` Simon Josefsson
2000-09-03 19:12 ` Arcady Genkin
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=87pumlhpsc.fsf@tea.thpoon.com \
--to=antipode@thpoon.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).