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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090717/c12ecb88/attachment-0002.bin>
Timo Sirainen wrote:> 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. >Yes; moving mail from an old source (for example, my old home dovecot server which still occasionally gets mail, but otherwise I don't really use it). I wouldn't want all my current mail sent to it for this purpose. ~Seth
On Jul 17, 2009, at 2:47 PM, Timo Sirainen wrote:> 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.Wow, that will be very handy! Thanks!!> 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.I think a two-way sync would be useful functionality to have, perhaps tied to a command line option, at least for the sake of completeness. It would also open up possibilities for having an "offline" IMAP server, which might be useful for mobile workgroups and such that may not always have full connectivity. -Dave -- Dave McGuire Port Charlotte, FL
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
Does this mean true multi master operation ? That would make configs with load balancers much easier :-) Timo Sirainen schrieb:> dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two > locations. Some things it can be used for:
Timo Sirainen wrote:> dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two > locations.I am very, very pleased to hear that you are working on this! Just at this moment, I am busy replacing a Dovecot IMAP based server with one with more powerful hardware, and until the tests are complete I want to operate both machines simultaneosly, so synchronisation is a big issue.> Does anyone want dsync to only sync changes from source to destination, > instead of doing a full two-way sync?If you want a decision "one-way XOR two-way", I'd definitely prefer the two-way sync option. If you can offer both sync types, all the better. BTW, if you have not yet planned to include them, I suggest exception lists. The default would be to sync all messages in all folders for a given list of users, right? It would be nice to be able to configure dsync to achieve the following, too: "Don't sync folders Trash, Junk, *.Newsletter, Boring.*" "Don't sync messages of a size greater than 2 MB" What do you think? -R