Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus Agent and mail
Date: Tue, 29 Apr 2003 00:40:00 -0500	[thread overview]
Message-ID: <usms1eua7.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87d6jk1flj.fsf@cam.ac.uk> (Gaute B. Strokkenes's message of "Fri, 18 Apr 2003 07:31:36 +0100")

Gaute B Strokkenes <gs234@cam.ac.uk> writes:

> On 14 apr 2003, kai.grossjohann@gmx.net wrote:
>>Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>>
>>>Now then, if you've severed your connection to the net, how do you
>>>intend to send your mail?
>>
>>Some people have an MTA on their machine which is able to queue mail
>>while offline.  Then the dialup script (or something like this) sends
>>the queued mails when connecting to the net.
>
> This is the default setup on Debian machines.  (It's not hard; if you
> have a reasonable MTA then it will deal with not being able to contact
> remote hosts right away.  The only `special' handling you need is to
> flush the mail queue from your ip-up script.)
>
> I used to have exactly this problem; I got some advice a couple of
> years ago from Kai (I think) which solved it for me.  Unfortunately I
> stopped using the Agent in the meanwhile so I can't work out what the
> solution was.
>
>>(That's how my Postfix setup works -- I use laptop-net to find out
>>whether there is a net connection.  But I still use the Agent to
>>queue mails inside Gnus -- that seemed to be easier to do.)
>
> 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.

I think that it would be better to change the code such that the
plugged status per server can be configured to either 1) always
plugged, 2) never plugged , or 3) plugged when gnus-plugged is t.

We're in the middle of a feature freeze right now.  I'll hang on to
this to consider later.

Kevin



  reply	other threads:[~2003-04-29  5:40 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 [this message]
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=usms1eua7.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).