If you have a single vmail UID, you can do: Mail_replica = mail processes need to have access to the replication-notify fifo and socket. Using SSH for example:ĭsync_remote_cmd = ssh -l% doveadm dsync-server -u%u You need to configure how and where to replicate. Replicator process should be started at startup, so it can start replicating users immediately: Mail_plugins = $mail_plugins notify replication Make sure that user listing is configured for your userdb, this is required by replication to find the list of users that are periodically replicated:Įnable the replication plugin globally (most likely you'll need to do this in nf): Another way to disable replication for some users is to return mail_replica field from userdb for users you want to replicate. Since v2.3.1 you can disable replication for a user by providing 'noreplicate' user database field. Fixing this is currently low priority for Dovecot developers. shared folders would likely need to lock the owner user, and public folders would likely need a per-folder lock or a maybe a global public folder lock). So this would need additional locks (e.g. But with shared folders multiple users can be syncing the same folder. This is because there's currently a per-user lock that prevents multiple dsyncs from working simultaneously on the same user. WARNING: Shared folder replication doesn't work correctly right now – mainly it can generate a lot of duplicate emails. The replication in general is a bit resource intensive, so it's not recommended to be used in multi-million user installations. This means that director isn't currently supported with replication. If you have a large cluster, you need multiple independently functioning Dovecot backend pairs. Replication works only between server pairs. This means that the more mails a mailbox has, the slower it is to sync it. Earlier versions can't do incremental metadata syncing. NOTE: v2.2 is highly recommended for this. The replication is done by looking at Dovecot index files (not what exists in filesystem), so no mails get lost due to filesystem corruption or an accidental rm -rf, they will simply be replicated back. The replication is done asynchronously, so high latency between the replicas isn't a problem. It's recommended that the same user always gets redirected to the same replica, but no changes get lost even if the same user modifies mails simultaneously on both replicas, some mails just might have to be redownloaded. Dovecot supports master/master replication using dsync.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |