Gnus development mailing list
 help / color / mirror / Atom feed
From: Joseph Barillari <jbarilla@research.bell-labs.com>
Subject: Salvaging Gcc when IMAP fails
Date: 11 Jul 2002 09:24:54 -0400	[thread overview]
Message-ID: <u4rf6jt21.fsf@research.bell-labs.com> (raw)

Occasionally, my at-work Gnus installation (5.9.0/GNU Emacs 21.2.1 for
Windows) drops its IMAP connection[0] during a session. This isn't a
big deal when I'm checking mail; I just hit `g' again when I receive
the error message, and Gnus merrily reconnects.

But when I'm sending a message, it's more of an irritation. My
installation Gcc's messages into an IMAP folder. If the connection
drops before I send a message, I get the following error:

Sending... 

error in process filter: imap-parse-response: Internal
error, tag 284 status BAD code nil text 
Server in unknown state for SELECT command error in process filter:
Internal error, tag 284 status BAD code nil text Server in unknown
state for SELECT command

imap-send-command-1: Process imap not running

The message is sent via SMTP, but it isn't Gcc'd. 

Is there any way to force the Gcc code to retry if the IMAP connection
is broken on the first attempt? Failing that, is there a command to
save the buffer of a just-sent message in a given mailbox?

Thanks in advance.

--Joe

[0] The IMAP server could be breaking the connection due to my
    inactivity, I haven't traced the initiator of the break. I'm
    running IMAP over SSL, if that makes a difference.
        




                 reply	other threads:[~2002-07-11 13:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=u4rf6jt21.fsf@research.bell-labs.com \
    --to=jbarilla@research.bell-labs.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).