Gcc when article is already mailed

Gcc when article is already mailed

[Nikolaus Rath]

Hello,

I just had the problem that I wrote a mail with Gcc to an nnimap
group. When I pressed C-c C-c, the nnimap connection had timed out, so
storing the mail in the Gcc group failed. Nevertheless the mail was
sent using smtp:

,----
| Sending...
| Sending via mail...
| Opening nnimap server...
| imap: Connecting to ebox.rath.org...
| Opening STARTTLS connection to `ebox.rath.org'...done
| imap: Connecting with STARTTLS...
| imap: Connecting to ebox.rath.org...failed
| Opening nnimap server...failed
| gnus-inews-do-gcc: Can't open server nnimap:
`----

Then I ended up in buffer containing the message. Restablishing the
imap connection was no problem in the server buffer, but I wasn't able
to figure out how to place the message in the group now. C-c C-c sends
the message by mail again.

Is there a way to store the message in the Gcc group afterwards that I
was unable to found? Otherwise I think that the message should not be
send at all if the Gcc group is not accessible.

Regards,

   --Nikolaus

-- 
»Perl - the only language that looks the same
 before and after RSA encryption.«           -- Keith Bostic

Re: Gcc when article is already mailed

[Jochen Küpper]

Nikolaus Rath <Nikolaus-BTH8mxji4b0@public.gmane.org> writes:

> I just had the problem that I wrote a mail with Gcc to an nnimap
> group. When I pressed C-c C-c, the nnimap connection had timed out, so
> storing the mail in the Gcc group failed. Nevertheless the mail was
> sent using smtp:

I've that problem when using my DSL-line quite often...

Simply undo-ing the message-buffer will bring back the Gcc: header
(which is removed for sending); a successive C-c C-c will ask to
resend the message where you can say "no", then the message is stored
in the Gcc folders anyway.

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)

Re: Gcc when article is already mailed

[Bjørn Mork]

Nikolaus Rath <Nikolaus@rath.org> writes:

> I just had the problem that I wrote a mail with Gcc to an nnimap
> group. When I pressed C-c C-c, the nnimap connection had timed out, so
> storing the mail in the Gcc group failed. Nevertheless the mail was
> sent using smtp:
>
> ,----
> | Sending...
> | Sending via mail...
> | Opening nnimap server...
> | imap: Connecting to ebox.rath.org...
> | Opening STARTTLS connection to `ebox.rath.org'...done
> | imap: Connecting with STARTTLS...
> | imap: Connecting to ebox.rath.org...failed
> | Opening nnimap server...failed
> | gnus-inews-do-gcc: Can't open server nnimap:
> `----
>
> Then I ended up in buffer containing the message. Restablishing the
> imap connection was no problem in the server buffer, but I wasn't able
> to figure out how to place the message in the group now. C-c C-c sends
> the message by mail again.
>
> Is there a way to store the message in the Gcc group afterwards that I
> was unable to found? Otherwise I think that the message should not be
> send at all if the Gcc group is not accessible.

I've used to work around this problem by modifying the original,
adding X- in front of "To:", "Cc:" and "Bcc:" to avoid resending the
message when hitting C-c C-c again. 

But it is a bit annoying and it would be nice if this could simply
Just Work(tm).  Either as you suggest, or at least by offering some
possibility of retrying the IMAP connection without also resending the
message via SMTP.

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?


Bjørn
-- 
Marxist!

Re: Gcc when article is already mailed

[Reiner Steib]

On Wed, Jun 14 2006, Jochen Küpper wrote:

> Nikolaus Rath <Nikolaus@rath.org> writes:
>
>> I just had the problem that I wrote a mail with Gcc to an nnimap
>> group. When I pressed C-c C-c, the nnimap connection had timed out, so
>> storing the mail in the Gcc group failed. Nevertheless the mail was
>> sent using smtp:
>
> I've that problem when using my DSL-line quite often...
>
> Simply undo-ing the message-buffer will bring back the Gcc: header
> (which is removed for sending); a successive C-c C-c will ask to
> resend the message where you can say "no", then the message is stored
> in the Gcc folders anyway.

Wouldn't `M-x gnus-inews-do-gcc RET' (more or less?) do that?

Maybe we'd have to prompt for the GCC argument (with completing) when
`gnus-inews-do-gcc' is called interactively.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Gcc when article is already mailed

[gdt]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]


  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?

To work, it will have to keep state about which has worked.  So
probably Gcc first, and delete the line on success, and then SMTP, so
then the nndraft: mechanism can handle queueing for both issues.

-- 
	Greg Troxel <gdt@work.lexort.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

Re: Gcc when article is already mailed

[Sam Steingold]

> * 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.