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-...@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
