D'oh. Replied to Timo instead of to the list. Apologies! On Thu, Nov 28, 2013 at 1:07 PM, David Bishop <dove...@dpe.lusars.net>wrote:
> On Thu, Nov 28, 2013 at 1:02 AM, Timo Sirainen <t...@iki.fi> wrote: > >> On 28.11.2013, at 5.17, David Bishop <dove...@dpe.lusars.net> wrote: >> >> > There are trams shuttling back and forth along this road (stopping at >> each >> > station), and adding a small box (such as a weatherproofed Raspberry Pi >> > with a wifi dongle) to transport files up and down the road is pretty >> > simple. >> >> But if you do it this way and you can keep a full copy of the shared mail >> storage on your Raspberry, that would be possible already with dsync I >> think. dsync supports quick incremental updates by keeping track of the >> previous state between the servers. This state is saved in a file, so you >> could keep a different state for each different dsynced server. >> > > Bravo for a solution that doesn't require a code change and doesn't seem > to require directly touching the spools! :) > > Reading the man page, it looks like only mirroring for people who happen > to be checking email at a given place (as well as people who have received > mail and the shared mailboxes) seems like a pretty simple thing to do. > Hurrah! > > Thank you, this is wonderful. > > And more questions... > > If I'm running a virtual mail domain, the user/pass I give is for the > virtual mail user, correct? And, in a virtual mail setup, do I specify > "username" or "username@domain"? > > Is there a window beyond which synchronization becomes more difficult? For > instance, if messages (or metadata updates, like "I deleted this message") > get parked overnight without updating, and in the morning (9 hours later), > the trams (one at a time) pull into range of wifi, there won't be > confusion, right? > >
