From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus Agent and mail
Date: Tue, 29 Apr 2003 21:12:20 -0500 [thread overview]
Message-ID: <ufzo04ttn.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84bryp9vbx.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Tue, 29 Apr 2003 17:28:34 +0200")
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Gaute B Strokkenes <gs234@cam.ac.uk> writes:
>>
>>> I think there ought to be an option to control whether or not the
>>> agent should queue mail--it seems easy to add, and it's clearly
>>> useful.
>>
>> While I agree with the intent, I don't like the idea of changing the
>> definition of gnus-plugged to cover every back-end EXCEPT imap.
>
> Hm?
>
> Gaute's suggestion wasn't to frob the IMAP behavior. Just that
> message-send-mail-function be different.
>
> At least that's my understanding.
Actually, Sean's original description was of setting a server
parameter to always plug his mail server. I'm not certain that that
works but he certainly expected it to.
Gaute did ask specifically about mail. I checked and the agent
controls mail queuing/sending in the function gnus-agent-send-mail.
In that function gnus-plugged is the controlling variable.
Now then, some unasked questions.
First, if a mail backend is configured (by some as yet unspecified
mechanism) to post messages while unplugged. How does it handle
fetching? Should it act like it's unplugged or plugged?
Second, if I have multiple mail servers, should I be able to configure
each individually?
My answers were such that individual mail servers could be configured
to act as if they were always plugged. At that point, I was one small
step from ANY server can be configured to be permanently plugged.
Kevin
next prev parent reply other threads:[~2003-04-30 2:12 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
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 [this message]
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=ufzo04ttn.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).