Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: "(ding)" <ding@gnus.org>
Subject: Re: nnagent
Date: 29 May 1997 06:52:16 -0700	[thread overview]
Message-ID: <864tbm4c8f.fsf@kramer.in.aventail.com> (raw)
In-Reply-To: Stainless Steel Rat's message of 28 May 1997 18:25:44 -0400

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 
> Lars> Uhm -- from the pop server, into the agent, and from there into nnml?
> Lars> Wouldn't that be a waste of perfectly good bauds?
> 
> It seems to be a waste to me.  The only rational way to use a POP server
> is to download everything from it to a local storage area, and every POP
> mail client that I know of -- including Forte's Agent -- operates on that
> premise.  The way that agent becomes a win is to queue up outgoing mail
> locally (which smtpmail and feedmail already accomplish) assuming that it
> will be made to do this.

  SPRY Mail has an option to only use what they call a 'remote inbox'.
They just download the header info from the messages and show the threaded
display of messages, then retrieve them one at a time as you try to read
them.  Sort of a poor-man's imap.

  It would be kind of nice to have a studly pop3 package that would allow
you to build this functionality into a backend.  but I'd rather see just
straight IMAP support. :)

  I solve the whole work/home laptop problem by just NFS mounting my home
directory from my laptop and symlinking my .gnus.el and .newsrc.eld files
over as well.  My .emacs has a few differences between work and home, and
lets my .gnus.el know what course of action to take.  Sort of like the
'profiles' in SPRY Mail.  I have it check different mail accounts, news
servers, and use different outgoing delivery methods (smtp vs. sendmail)
depending on whether I am at work, on the bus, or at home.  Works pretty
well.

-Bill P.


      parent reply	other threads:[~1997-05-29 13:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-28  8:51 nnagent Greg Stark
1997-05-28 19:57 ` nnagent Lars Magne Ingebrigtsen
1997-05-28 21:53   ` nnagent Greg Stark
1997-05-29  7:52     ` nnagent Lars Magne Ingebrigtsen
1997-05-30  8:51       ` nnagent Kai Grossjohann
     [not found]   ` <x7soz7dyjb.fsf@peorth.gweep.net>
1997-05-29  7:54     ` nnagent Lars Magne Ingebrigtsen
1997-05-29 10:26       ` nnagent Steinar Bang
1997-05-29 21:48         ` nnagent Lars Magne Ingebrigtsen
1997-05-30  6:49           ` nnagent Steinar Bang
1997-05-30 10:18             ` nnagent Steinar Bang
1997-05-30 20:34               ` nnagent Lars Magne Ingebrigtsen
1997-06-01 19:35                 ` nnagent Steinar Bang
1997-06-02 12:09                   ` nnagent Per Abrahamsen
1997-06-02 12:48                     ` nnagent Kai Grossjohann
1997-06-03  6:54                     ` nnagent Steinar Bang
1997-06-03  7:02                       ` nnagent Kai Grossjohann
1997-06-03 10:45                         ` nnagent Steinar Bang
1997-05-29 12:50       ` nndraft (was: Re: nnagent) Per Abrahamsen
1997-05-29 21:51         ` Lars Magne Ingebrigtsen
1997-05-30  2:35           ` Sudish Joseph
1997-05-30 20:27             ` Lars Magne Ingebrigtsen
1997-05-29 13:52     ` William M. Perry [this message]

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=864tbm4c8f.fsf@kramer.in.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@gnus.org \
    /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).