From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] New to Sup and some imap sync questions
Date: Wed, 29 Apr 2009 11:09:16 -0700 [thread overview]
Message-ID: <1241028139-sup-8070@entry> (raw)
In-Reply-To: <1241024581-sup-9014@javelin>
Reformatted excerpts from Edward Z. Yang's message of 2009-04-29:
> My current understanding is that William is not interested in mucking
> around with IMAP any more than he has to, so unless someone steps up
> and submits some patches there will not be syncing back to IMAP.
That's pretty much the case, but I hope it's ameliorated by the fact
that I do plan to get sup-sync-back working with Maildir ("any day
now"), and then you can use offlineimap to really sync between IMAP and
Sup.
> As for handling Sup on multiple machines, I think the current best
> practice is "don't"; pick one machine, make it ssh'able into, and use
> that to handle all of your mail.
Correct.
Recently I've been thinking about the possibility of storing one's
mbox/Maildir in git, syncing it between machines (Maildir would probably
work best for this, as mbox will generate spurious conflicts when
deleting+adding), and maintaining the Ferret index locally on each
machine. If we add a notion of an outbound message queue to Sup (i.e.
each machine knows whether it has the ability to send mail or not), and
also synchronize that and the drafts and sent folders between machines,
you could use Sup for completely offline, distributed email. Crazy?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-29 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:49 Christopher Bertels
2009-04-29 17:04 ` Edward Z. Yang
2009-04-29 18:09 ` William Morgan [this message]
2009-04-29 18:38 ` Edward Z. Yang
2009-04-29 20:16 ` William Morgan
2009-04-29 20:58 ` William Morgan
2009-04-29 20:48 ` Christopher Bertels
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=1241028139-sup-8070@entry \
--to=wmorgan-sup@masanjin.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