search for: mail_replica

...now if it is possible to sync/replicate only >>>> specific >>>> domain(users)? or it's always the whole lot? >>> See >>> http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html >>> >>> >>> basically set 'mail_replica' to 'remote:server3' in your >>> userdb >>> >>> >>> B >>> >> thanks B, >> userdb as appose to plugin? >> it's quite unclear what to put there, to a beginner. >> > also if I put mail_replica (having the rest, pr...

Silly question but regarding https://wiki.dovecot.org/Replication, is the mail_replica parameter shown in the docs equivalent to replicator_host and replicator_port in 2.3.3 ? 2.3.3 doesn't seem to like the mail_replica param (and indeed doveconf -a doesn't show it as an option) Thanks !

...y, they cost double! Even if you have 20 servers, when one goes down all that IO traffic goes to just one. > So, what I did here was a (kind of) DHT-based n-way replication, where the node for the second copy is independent of where the first copy is. > For that you will have to use the mail_replica inside your userdb. Here I'm using MySQL. The catch is that the mail_replica is now always the same for the same user. The first server need a mail_replica pointing to the second while the second need a mail_replica pointing to the first. In order to do that I have a table with two fields: host...

Hi all, I've been researching ways to replicate mail across multiple mailstores and have a few questions. Synching 2 mailstores (M1 & M2) via dsync works fine. I want to add a 3rd and 4th (M3 & M4) server to also be synced. Multi-sync (>2 servers): 1) How do I tell M1 and/or M2 to also sync to M3 and/or M4? Selective sync: 2) How do I sync specific domains to specific

...9;ve barely started reading on dsync and I wonder.. >> would you know if it is possible to sync/replicate only specific >> domain(users)? or it's always the whole lot? > See > http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html > > basically set 'mail_replica' to 'remote:server3' in your userdb > > > B > thanks B, userdb as appose to plugin? it's quite unclear what to put there, to a beginner.

Hi Mike, Is the value of the 'doveadm_port' if I am choosing: mail_replica = tcp:server1.domain.ltd no ? I might be wrong too ;) Thx Le mardi 24 janvier 2017 ? 11:41:28, vous ?criviez : > Hello, > I might be wrong, but the port which will be used for the replicator > port is the value of 'doveadm_port' which in your case is 4711. > Mike; >...

...arallel (10 by default) replication_max_conns = 10 # tell doveadm client to use this port by default doveadm_port = 4711 #Both the client and the server also need to have a shared secret doveadm_password = {SHA512-CRYPT}$6$rou.................... # use tcp:hostname as the dsync target plugin { #mail_replica = tcp:server2.domain.ltd # use doveadm_port mail_replica = tcp:server2.domain.ltd:12345 # use port 12345 explicitly } service config { unix_listener config { user = vmail } } *************************************************************************************** dsync config server2.do...

Is there anyway of replicating between more than one other instance of Dovecot. I have bidirectional replication working successfully and it seems to be reliable. I would like to replicate from one or more of these instances to one other. Is this possible? Dirk

...= no ssl_key = </etc/ssl/private/private.key ssl_cert = </etc/ssl/certs/key.crt ssl_client_ca_file = </etc/ssl/certs/GandiCA2.pem # Create a listener for doveadm-server service doveadm { user = vmail inet_listener { port = 12345 ssl= yes } } and doveadm_port = 12345 // mail_replica = tcps:server2.domain.ltd # use doveadm_port And now: Feb 03 14:11:16 doveadm(user1 at domain.ltd): Error: sync: Couldn't initialize SSL context: Can't load CA certs from directory : error:02001024:system library:fopen:File name too long Feb 03 14:11:17 doveadm: Error: Corrupted SSL param...

Hello, Still working with my dsync pb. I have done a clone (vmware) of my email server. Today I have two strictly identical emails servers (server1 (main) and server2 (bck) (except IP, hostname and mail_replica). The ssl config on my both server: ssl_protocols = !SSLv2 !SSLv3 ssl = required verbose_ssl = no ssl_key = </etc/ssl/private/private.key ssl_cert = </etc/ssl/certs/key.crt ssl_ca = </etc/ssl/certs/GandiStandardSSLCA2.pem This config is working for my email client and my email...

...unk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=sha512-crypt /usr/local/etc/creds driver = passwd-file } plugin { mail_replica = tcps:mx2.example.com:12345 } protocols = " imap" replication_full_sync_interval = 1 hours service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service doveadm { inet_listener { port = 12345...

...dovecot.conf file. I do not see "/etc/dovecot/conf.d/12-replication.conf" in my servers. So I had put everything in the dovecot.conf file only. Please see the complete data in it below. The below data is in server A. In other server (server B) Also I have the same configuration, except mail_replica line and it is pointing to the other server like, " mail_replica = remote:vmail at bal3200dev001.testorg.com ". I have generated/configured the ssh keys also for vmail user in both servers. Now When i manually ssh to the server, it is not asking for a password. ===================== ===...

...would you know if it is possible to sync/replicate only specific >>>>> domain(users)? or it's always the whole lot? >>>> See >>>> http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html >>>> >>>> basically set 'mail_replica' to 'remote:server3' in your userdb >>>> >>>> >>>> B >>>> >>> thanks B, >>> userdb as appose to plugin? >>> it's quite unclear what to put there, to a beginner. >>> >> also if I put mail_replic...

Thank you for the reply. I have done the sync manually with "doveadm sync" command. But, I have not configured the replication yet. I am looking at the below webpage for the replication. https://wiki.dovecot.org/Replication I am using the dovecot version "2.2.36". I am confused with what needs to be done after reading that page. 1. They are talking about v2.3.1 and v2.2+.

...ction type. These errors never occur if non-encrypted tcp is configured. I've been able to validate this by changing only the replica_type on both ends of the replication configuration to tcp, and with no other changes and after a few days of operation there is not a single error logged. mail_replica = tcps:lightning.reub.net:4813 <<< periodic timeouts mail_replica = tcp:lightning.reub.net:4814 <<< works perfectly Example of the error: Jun 12 15:45:44 thunderstorm.reub.net dovecot[21149]: dsync-local(kaylene)<zx+WKTAU416UMwAAzkCIew>: Error: dsync(lightning.reub.n...

...ying to connect to the other server via SSH. Is that normal? Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l vmail backup.host.ee doveadm dsync-server -D -u user at host.ee Then I ended up setting mail_replica in userdb for only my test user, but I could still see in the logs that it was trying to sync the others as well, despite mail_replica being 0 for the rest. Jun 22 20:52:59 host dovecot: doveadm(user at host.ee): Fatal: -N parameter requires syncing with remote host I also notice (and read fro...

...Pairs are ugly, they cost double! Even if you have 20 servers, when one goes down all that IO traffic goes to just one. So, what I did here was a (kind of) DHT-based n-way replication, where the node for the second copy is independent of where the first copy is. For that you will have to use the mail_replica inside your userdb. Here I'm using MySQL. The catch is that the mail_replica is now always the same for the same user. The first server need a mail_replica pointing to the second while the second need a mail_replica pointing to the first. In order to do that I have a table with two fields: host...

...says that it shouldn't be a problem because it will use do a passdb lookup instead (except for PAM which isn't used here). Unfortunately, it's not working. I've testing with ssh : dsync_remote_cmd = ssh -l vmail %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} mail_replica = remote:vmail at server2.domain.com as well as with straight tcp (SSL for later) mail_replica = tcp:server2.domain.com:999 /var/log/mail.err shows the problems ... Jun 3 11:30:53 server1 dovecot: auth: Error: Trying to iterate users, but userdbs don't support it Jun 3 11:30:53 server1...

Hi ? I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } | local> host remote.test: remote.test has IPv6 address fd00:b::1 working well. Currently: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { ad...

...ywhere anywhere tcp dpt:4711 Is it the FW who is really blocking this port ? Or something else ?? Any ideas ? Thx for your support. Le mardi 24 janvier 2017 ? 11:45:14, vous ?criviez : > Hi Mike, > Is the value of the 'doveadm_port' if I am choosing: mail_replica = > tcp:server1.domain.ltd no ? > I might be wrong too ;) > Thx > Le mardi 24 janvier 2017 ? 11:41:28, vous ?criviez : >> Hello, >> I might be wrong, but the port which will be used for the replicator >> port is the value of 'doveadm_port' which in your...