From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87087 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: How do you manage the "nndraft:queue" folder? Date: Thu, 09 Jun 2016 09:27:21 +0800 Message-ID: <87bn3byww6.fsf@ericabrahamsen.net> References: <87h9d46iy0.fsf@aol.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1465435746 25352 80.91.229.3 (9 Jun 2016 01:29:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Jun 2016 01:29:06 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M35307@lists.math.uh.edu Thu Jun 09 03:28:54 2016 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bAomC-0003bF-DI for ding-account@gmane.org; Thu, 09 Jun 2016 03:28:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.86_2) (envelope-from ) id 1bAokz-0002o5-QU; Wed, 08 Jun 2016 20:27:37 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86_2) (envelope-from ) id 1bAokw-0002nZ-5g for ding@lists.math.uh.edu; Wed, 08 Jun 2016 20:27:34 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_2) (envelope-from ) id 1bAoku-0007in-N1 for ding@lists.math.uh.edu; Wed, 08 Jun 2016 20:27:34 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1bAokt-0007mr-AA for ding@gnus.org; Thu, 09 Jun 2016 03:27:31 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bAokr-0002n8-UG for ding@gnus.org; Thu, 09 Jun 2016 03:27:30 +0200 Original-Received: from 61.149.187.167 ([61.149.187.167]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 09 Jun 2016 03:27:29 +0200 Original-Received: from eric by 61.149.187.167 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 09 Jun 2016 03:27:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 59 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 61.149.187.167 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:AGEKdHUV9JjYv56Qi0N+2LAOEUk= X-Spam-Score: -1.7 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87087 Archived-At: Live System User writes: > Hi, > > How does one manage the "nndraft:queue" folder? Sent messages go into the queue when Gnus is in an "unplugged" state. You can toggle the plugged state with the "J j" binding in the *Group* buffer. When Gnus is plugged, you can send everything in the queue folder with "J S". > Is there a way for Gnus to indicate to you that there > are messages queued in the "nndraft:queue" folder that > need processing either notifying periodically and/or > when subsequently invoking Gnus again later on? I only > noticed that there was a message in my "nndraft:queue" > folder" because of a problem that I tried to report that > hung while sending and had to C-g and tried again and got > the message: > > Denied posting -- multiple copies > > The "*unsent..." buffer remained. There should be an "unread message" count on the queue group, same as other groups. > If there are multiple messages in the "nndraft:queue" folder, > is there a way to *ONLY* send particular queued messages or > is it an all-or-nothing situation? Is it possible to mark > some messages then having *only* those messages sent? I haven't tried this, but it's likely that the regular draft commands work in the queue as well. Try going into the queue group and using "D s" on a message you want to send. > Can you manually queue a newly composed message *without* it > being sent immediately? Can you set some option temporarily > so that all subsequent messages get queued until you change > that option to say "deliver any newly created messages now > but not any that were already queued beforehand"? Toggling the plugged state is the normal way to do this: toggle unplugged, send a bunch of messages, toggle plugged, then send the queue. Another option is delaying the messages: see the "Delayed Articles" section of the Gnus manual. > How can one setup Gnus to send messages base on a condition(s) > like when on Wi-Fi, between specific hours, when on ethernet > and the size of the message is greater than a particular > threshold, etc.? You'd need to do this yourself: set up a timer, and run a function on the timer that checks for your condition. > Are these possible to do with Gnus *without* requiring the > use of a local SMTP server? You always need a SMTP server, but it doesn't need to be local.