[Dovecot] dsync - one or two ways?

[joakim at verona.se]

Timo Sirainen <tss at iki.fi> writes:

> dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two
> locations. Some things it can be used for:
>
>  - Initially transfer a mailbox to another server via SSH
>  - A faster sync done to an existing mailbox, sending only changes
>  - A superfast sync based on modification sequences.
>  - Source and destination mailboxes can use different formats
> (convert-tool will be history)
>
> dsync can handle all kinds of conflicts in mailboxes, handle mailbox
> deletions, renames, etc. So it's safe to sync even if both source and
> destination mailboxes have had all kinds of changes.
>
> Now, the question is: Does anyone want dsync to only sync changes from
> source to destination, instead of doing a full two-way sync? I think in
> typical cases where you'd think you would want only one-way sync are
> also the cases where there's no changes coming the other way in any
> case.
>

This sounds really awesome! How testable is it?
My setup would be:
- one server dovecot that is online all the time, filtering email to several
mailboxes with sieve scripts
  - the server dovecot would receive changes through a webmail instance
- a dovecot running on my laptop that I would like to be in sync with
the server dovecot. I read mail there with Gnus.

Theres only a one user(me) that would have this setup, but there are
a handful of other users as well. I have a couple of hundred mailboxes
to sync. Can all mailboxes be synced automatically, or do I need to make
a list of them for dsync?

-- 
Joakim Verona