The addition of this feature is basically only clustering of the /etc/virtual/domain.com/passwd file, using the API.. so when a Client creates an account on box1, DA calls the API on box2 as "admin|user", so you must have already created "user" on box2 with the same domain.
It's a very small piece of the puzzle, the rest is still up to you (matching creation of Users, domains, and syncing of email data, as well as any MX settings you want to do).
Again, the feature added is not a complete solution to the feature of "full remote email control/clustering".
@Trickster: It's not really related to MX fail-over, as the accounts would exist on box2, so they're going to stay on box2 if they arrive there.
I would assume the main uses would be
- if you need a 100% stand-alone mail server with DA on it, and want to keep them in sync
- if you have a 2nd backup/standby server that you want to keep as in sync as possible.
but as it's a tool that does 1 specific task, I'm sure others will find other ways of using it to their advantage.
John