Gnus development mailing list
 help / color / mirror / Atom feed
From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: road warrior trying to simplify a mail setup
Date: Fri, 07 Feb 2003 13:49:42 -0500	[thread overview]
Message-ID: <u8zbs1oncxl.fsf@blackbird-2k.MITRE.ORG> (raw)
In-Reply-To: <86isvw2c1b.fsf@red.stonehenge.com> (merlyn@stonehenge.com's message of "07 Feb 2003 10:14:40 -0800")

>>>>> On 07 Feb 2003 10:14:40 -0800, merlyn@stonehenge.com (Randal L. Schwartz) said:

>>>>> "David" == David S Goldberg <david.goldberg6@verizon.net> writes:
David> For what it's worth, I keep my .News and .newsrc* files in synch
David> between several machines.  I prefer unison to rsync (unison is based
David> on rsync protocol, but provides bidirectional synchronization and
David> offers a merging capability (by calling emacs, of course :-).

> How does that work for offline delivery and agent mode?

In my case it's orthogonal.  Delivery goes into an IMAP server at work
which I can get to from three different places when I am at work: a
w2k laptop, a relatively standalone linux box, or any number of UNIX
(Sun, Linux, SGI) machines which access my home directory via AFS.  I
can also get to it via VPN or ssh from my home system but I choose not
to do that.  I use unison to keep all three work systems in sync.  In
the worst case, I read mail on one system and then on another without
sync'ing.  In that case, I lose out on updates to score files and
.newsrc.eld which is mostly minor annoyance.  I do not keep the
cache/agent in sync on them.  Since I only really use the agent on my
laptop it's not worth copying it over to the others.  I'm not sure
what you mean by off line delivery.  When I'm off line, the mail gets
delivered as it always does but I can't see it until I'm back on line.
But I know that you know that so there must be something else to the
term.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net





  reply	other threads:[~2003-02-07 18:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 17:04 Randal L. Schwartz
2003-02-05 21:47 ` Vasily Korytov
2003-02-05 21:49   ` Randal L. Schwartz
2003-02-06  9:30     ` James Leifer
2003-02-06 21:37     ` Kirk Strauser
2003-02-06 15:46 ` Kai Großjohann
2003-02-07  1:27 ` Stainless Steel Rat
2003-02-07  2:04   ` Randal L. Schwartz
2003-02-07  2:24     ` Stainless Steel Rat
2003-02-07  5:41       ` Randal L. Schwartz
2003-02-07 16:28         ` Stainless Steel Rat
2003-02-07 16:39           ` David S Goldberg
2003-02-07 18:14             ` Randal L. Schwartz
2003-02-07 18:49               ` David S Goldberg [this message]
2003-02-07 18:13           ` Randal L. Schwartz
2003-02-07 19:38             ` Stainless Steel Rat
2003-02-07 19:53               ` Randal L. Schwartz
2003-02-07 20:06                 ` Stainless Steel Rat
2003-02-07 20:18                   ` Randal L. Schwartz
2003-02-07 23:18                     ` Stainless Steel Rat
2003-02-07 21:45             ` Kai Großjohann
2003-02-07  7:18 ` Michel Schinz
2003-02-07  9:07   ` Niklas Morberg
2003-02-07 15:44     ` Randal L. Schwartz
2003-02-07 16:34       ` David S Goldberg
2003-02-07 15:52   ` Kai Großjohann
2003-02-14 21:53 ` David Wuertele
2003-02-15  5:50   ` Randal L. Schwartz
2003-02-15  6:02     ` Randal L. Schwartz
2003-03-01  0:32       ` David Wuertele
2003-03-03  8:50         ` Bjørn Mork
2003-03-03 17:27           ` David Wuertele
2003-03-04 12:11             ` Bjørn Mork

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=u8zbs1oncxl.fsf@blackbird-2k.MITRE.ORG \
    --to=david.goldberg6@verizon.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).