From: Sean Neakums <sneakums@zork.net>
Subject: Re: Gnus Agent and mail
Date: Fri, 24 Jan 2003 13:49:59 +0000 [thread overview]
Message-ID: <6ur8b27j3s.fsf@zork.zork.net> (raw)
In-Reply-To: <84k7gulngu.fsf@lucy.is.informatik.uni-duisburg.de>
commence Kai Großjohann quotation:
> Sean Neakums <sneakums@zork.net> writes:
>
>> What is the current method to prevent sent mail from being queued
>> when the Agent is active? My mail select method is not covered by
>> the Agent, and both message-send-mail-function and
>> gnus-agent-send-mail-function are set to
>> message-send-mail-with-sendmail, but when I send mail, it is
>> queued.
>
> There is a recent variable message-send-mail-real-function.
Aha, so there is. It would be nice if the Agent could be told
directly whether to queue mail or not. Here is a small patch that
adds and uses a customization for this. There may be issues I haven't
considered, though.
Index: gnus-agent.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-agent.el,v
retrieving revision 6.134
diff -u -r6.134 gnus-agent.el
--- gnus-agent.el 22 Jan 2003 05:30:47 -0000 6.134
+++ gnus-agent.el 24 Jan 2003 13:47:40 -0000
@@ -146,6 +146,11 @@
:group 'gnus-agent
:type 'integer)
+(defcustom gnus-agent-queue-mail-when-unplugged t
+ "Set to nil to prevent the Agent from queueing sent mail."
+ :group 'gnus-agent
+ :type 'boolean)
+
;;; Internal variables
(defvar gnus-agent-history-buffers nil)
@@ -438,10 +443,11 @@
(gnus-open-agent)
(add-hook 'gnus-setup-news-hook 'gnus-agent-queue-setup)
(unless gnus-agent-send-mail-function
- (setq gnus-agent-send-mail-function (or
- message-send-mail-real-function
- message-send-mail-function)
- message-send-mail-real-function 'gnus-agent-send-mail))
+ (if gnus-agent-queue-mail-when-unplugged
+ (setq gnus-agent-send-mail-function (or
+ message-send-mail-real-function
+ message-send-mail-function)
+ message-send-mail-real-function 'gnus-agent-send-mail)))
(unless gnus-agent-covered-methods
(mapcar
(lambda (server)
--
/ |
[|] Sean Neakums | Size *does* matter.
[|] <sneakums@zork.net> | That's why I use Emacs.
\ |
next prev parent reply other threads:[~2003-01-24 13:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 8:33 Sean Neakums
2003-01-24 12:52 ` Kai Großjohann
2003-01-24 13:49 ` Sean Neakums [this message]
2003-01-24 22:00 ` Lars Magne Ingebrigtsen
2003-04-13 21:10 ` Kevin Greiner
2003-04-13 21:18 ` Sean Neakums
2003-04-13 23:32 ` Kevin Greiner
2003-04-14 6:15 ` Kai Großjohann
2003-04-18 6:31 ` Gaute B Strokkenes
2003-04-29 5:40 ` Kevin Greiner
2003-04-29 15:28 ` Kai Großjohann
2003-04-30 2:12 ` Kevin Greiner
2003-05-01 10:57 ` Kai Großjohann
2003-05-08 23:36 ` Gaute B Strokkenes
2003-05-10 14:43 ` Kevin Greiner
2003-05-10 16:08 ` Gaute B Strokkenes
2003-05-10 22:21 ` Gaute B Strokkenes
2003-05-11 23:20 ` Kevin Greiner
2003-05-12 5:52 ` Gaute B Strokkenes
2003-05-12 13:47 ` Kevin Greiner
2003-05-12 18:46 ` Gaute B Strokkenes
2003-05-12 20:37 ` Gaute B Strokkenes
2003-05-14 11:07 ` Gaute B Strokkenes
2003-05-14 17:15 ` Kevin Greiner
2003-05-14 20:15 ` Gaute B Strokkenes
2003-05-15 8:15 ` Gaute B Strokkenes
2003-05-12 15:51 ` Kai Großjohann
2003-05-12 18:49 ` Gaute B Strokkenes
2003-05-13 12:31 ` Kai Großjohann
2003-05-10 17:35 ` Kai Großjohann
2003-05-10 20:54 ` Gaute B Strokkenes
2003-05-12 15:49 ` Kai Großjohann
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=6ur8b27j3s.fsf@zork.zork.net \
--to=sneakums@zork.net \
/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).