Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <>
Subject: Re: message-dont-send in queue folder not in draft folder
Date: Thu, 14 Dec 2023 14:06:02 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

>>> "ESF" == Eric S Fraga <> writes:

> I don't understand the issue here (or did not understand your original
> post).

> When I compose an email unplugged, if I don't send it (C-c C-d), it goes
> in drafts; if I send it (C-c C-c), it goes in the queue.  How is your
> needs different from the default behaviour?

My problem is that my draft folder contains some 20 messages, basically
messages that are half done.

But sometimes I write 2 emails one after another, but I want to send
both say 2 hours later. Of course I can save them in the draft folder
but since that folder contains say 20 message. I don't find this

Best would be to save these messages in the queue folder since it
remains me later to send these messages. 

Now I could unplug gnus write these messages «send» them and plugin gnus
again. But I prefer to have gnus plugged in almost always, since some
message might arrive in the meantime.

I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2023-12-14 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 13:09 Uwe Brauer
2023-12-13 15:46 ` Uwe Brauer
2023-12-13 16:25   ` Eric Abrahamsen
2023-12-14 13:08     ` Uwe Brauer
2023-12-15  1:45       ` Eric Abrahamsen
2023-12-15  6:42         ` Uwe Brauer
2023-12-13 16:31   ` Eric S Fraga
2023-12-14 13:06     ` Uwe Brauer [this message]
2023-12-14 13:21       ` Eric S Fraga
2023-12-14 17:17         ` Uwe Brauer
2023-12-14 14:44       ` Tim Landscheidt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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