From: James Leifer <James.Leifer@inria.fr>
Subject: Re: road warrior trying to simplify a mail setup
Date: Thu, 06 Feb 2003 10:30:05 +0100 [thread overview]
Message-ID: <r77fzr1rc2q.fsf@brouilly.inria.fr> (raw)
In-Reply-To: <86smv2bdpb.fsf@red.stonehenge.com> (merlyn@stonehenge.com's message of "05 Feb 2003 13:49:20 -0800")
[long reply...]
Greetings!
I face a similar problem of synchronising my mail on two machines that
are often offline.
I have been considering using nnmaildir to manage all mail (one
message per file). If I understand Paul Jarc's description correctly,
this has the advantage of storing each message's mark in a separate
file (not together in a big .newsrc). If so, then I could use unison
(which already synchronises bidirectionally my 600 MB home directory
in seconds) for the mails and marks. Anyone tried this?
Unison is at: http://www.cis.upenn.edu/~bcpierce/unison/ .
Another interesting tool I noticed (but haven't had time to play with)
is offlineimap: http://gopher.quux.org:70/devel/offlineimap/
As far as I understand it, an ideal scenario looks like this:
(1) Imagine two machines, A and B, that can connect to each other
from time to time, each of which has a complete replica of my
mail.
(2) I make changes on machine A involving both the physical messages
(moves between groups, creation of new gcc'd messages, deletes,
etc.) and the marks (read, replied, etc.), with gnus keeping a
log of what has changed.
(3) Likewise, I make changes on machine B.
(4) I connect A and B and some tool merges the two change logs and
then (bidirectionally) copies and deletes files so that the
replicas are again identical. The merging might have to deal
with conflicts that I need to resolve manually (e.g. on one
replica I have deleted a message, on the other I have moved it to
another group).
What would it involve to implement?
(2) requires gnus to keep logs of message and mark changes. Can the
agent do this? (It might need to record things like "message with
message-id x and hash y and file name z has moved from group c to
group d".)
(4) requires a tool to parse the log files and ask about conflicts.
The actual copying could then be handled by unison.
Anyone tried this?
Regards,
--
James Leifer, INRIA Rocquencourt, France
next prev parent reply other threads:[~2003-02-06 9:30 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 [this message]
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
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=r77fzr1rc2q.fsf@brouilly.inria.fr \
--to=james.leifer@inria.fr \
/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).