Re: Gcc when article is already mailed

[Sam Steingold <sds@podval.org>]

> * Bjørn Mork <ozbex@qbq.ab> [2006-06-14 14:57:00 +0200]:
>
> I guess there is a reason why it does things this way: Gnus can't know
> that the Gcc will fail before trying it, at which time the message has
> already been sent to via SMTP.  Maybe trying Gcc first would be an
> acceptable fix?  Does it have any downside?  I guess it will cause the
> reversed problem: Gcc works but SMTP fails.  But that would probably
> be better, given enough warning so that the user knows the message was
> not sent.  Or?

before trying GCC, gnus should check if the server is open, and, if not,
it should try to re-open it.

in general, this is not a magic bullet: if the server is down, then any
operation will involving it will take a lot of time: an attempt to
re-open it instead of an immediate error.

the real solution is to allow user to "disable" a server without
removing it permanently.
if a server is disabled, then any operation involving it should not
signal an error but display a warning instead - and proceed with the
rest of a command.
if a server is closed, any operation on it should start with a re-open
attempt, and if that fails, a user should be presented with an error
message suggesting to disable the server, and to remember to re-enable
it later.

-- 
Sam Steingold (http://www.podval.org/~sds) on Fedora Core release 5 (Bordeaux)
http://pmw.org.il http://truepeace.org http://memri.org http://mideasttruth.com
http://jihadwatch.org http://palestinefacts.org http://camera.org
I'd give my right arm to be ambidextrous.