From: gdt@work.lexort.com
Cc: ding@gnus.org
Subject: Re: Gcc when article is already mailed
Date: Wed, 14 Jun 2006 09:34:44 -0400 [thread overview]
Message-ID: <smuodwvc13f.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <8764j3nbdv.fsf@obelix.mork.no> (=?iso-8859-1?Q?Bj=F8rn?= Mork's message of "Wed, 14 Jun 2006 14:57:00 +0200")
[-- 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 --]
next prev parent reply other threads:[~2006-06-14 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:42 Nikolaus Rath
[not found] ` <87y7w06k05.fsf-1YnPVixzkSuL2G7IJ6k9tw@public.gmane.org>
2006-06-14 12:50 ` Jochen Küpper
2006-06-14 13:23 ` Reiner Steib
2006-06-14 12:57 ` Bjørn Mork
2006-06-14 13:34 ` gdt [this message]
2006-06-14 13:57 ` Sam Steingold
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=smuodwvc13f.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--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).