search for: mail_replicas

Displaying 20 results from an estimated 310 matches for "mail_replicas".

Did you mean: mail_replica
2015 Jun 17
4
dsync selectively
On 16/06/15 14:27, lejeczek wrote: > On 16/06/15 14:16, lejeczek wrote: >> On 16/06/15 13:14, B wrote: >>> P, >>> >>> On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote: >>> >>>> I've barely started reading on dsync and I wonder.. >>>> would you know if it is possible to sync/replicate only >>>> specific
2019 Jul 03
1
mail_replica equivalent to replicator_host/replicator_port
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 !
2015 May 31
1
multi sync (>2 servers) + selective sync + trigger
Daniel, On Sat, May 30, 2015 at 09:26:32AM -0300, Daniel van Ham Colchete wrote: > B, > I really like the idea of N-way replication. 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
2015 May 29
2
multi sync (>2 servers) + selective sync + trigger
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
2015 Jun 16
2
dsync selectively
On 16/06/15 13:14, B wrote: > P, > > On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote: > >> I'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 >
2017 Jan 24
3
dsync dovecot / Failed connection refused
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; > On 01/23/2017
2017 Jan 23
2
dsync dovecot / Failed connection refused
Dear all, I am using VMWare and I have cloned my emails server. Now I do have two identicals servers, both running the same version of dovecot (2.2.13) and imap. Let's call them: server1.domain.ltd and server2.domain.ltd. I would like to sync both server using dsync. Dovecot is working well except concerning the sync. dsync config server1.domain.ltd # Enable the replication plugin
2015 Sep 02
1
more than two way replication
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
2017 Feb 03
4
Dovecot dsync 'ssl_client_ca'
Hi, I have made change: ssl_protocols = !SSLv2 !SSLv3 ssl = required verbose_ssl = 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 =
2017 Feb 03
3
Dovecot dsync 'ssl_client_ca'
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 =
2020 Nov 18
0
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hello, I have two mail servers and am also experiencing sporadic replication errors over tcps, similar to Reuben. Each server is running Dovecot 2.3.11.3 (502c39af9) on Debian 10.6. *Log entries from MX1* Nov 18 00:39:26 mx1 dovecot: dsync-local(user at example.com)<Ow3zAjWxtF+TDgAAPHKnuQ>: Error: dsync(mx2.example.com): I/O has stalled, no activity for 600 seconds (last sent=mailbox,
2020 Jul 17
2
Stuck here - help please
Hi Gerald, Thank you for the details. As per your suggestion, I have made the changes to dovecot.conf file. Still I don't see any replication is happening. Please see the 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
2015 Jun 18
0
dsync selectively
On 06/17/2015 06:07 PM, lejeczek wrote: > On 16/06/15 14:27, lejeczek wrote: >> On 16/06/15 14:16, lejeczek wrote: >>> On 16/06/15 13:14, B wrote: >>>> P, >>>> >>>> On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote: >>>> >>>>> I've barely started reading on dsync and I wonder.. >>>>> would
2020 Jul 16
2
Stuck here - help please
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+.
2020 Jun 13
2
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hi, I've been seeing errors logged for some time with replication processes, whereby replication sessions seem to be timing out periodically. This is with dovecot version 2.3.10.1 (a3d0e1171) and both are Gentoo x86_64. After some investigation I've determined that these timeouts are only ever occurring with tcps as the replication connection type. These errors never occur if
2019 Jun 22
2
Dovecot replication and userdb "noreplicate".
Hello! I finally took the time and spent two days to set up replication for my server and now I have a question or two. I initially set noreplicate userdb field to 1 for all but a test user, but I could still see in the logs that all mailboxes were trying 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
2015 May 30
0
multi sync (>2 servers) + selective sync + trigger
B, I really like the idea of N-way replication. 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
2014 Jun 03
2
Replication with virtual users and static userdb possible ?
Is it possible to get replication working in a virtual user setup that uses a static userdb ? My environment is fairly simple and typical - there's a single system user (vmail) that owns all the home dirs (/var/mail/domain.com/user). The virtual users (userid at domain.com:secretpassword) are kept in a single file (/var/mail/domain.com/PASSWD) that's unique per domain, and referenced as a
2016 Dec 28
0
IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused
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 = [::] } } |
2017 Jan 26
0
dsync dovecot / Failed connection refused
Hi, Jan 26 17:21:40 doveadm(user7 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:23:59 doveadm(user3 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user5 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user4 at domain.ltd): Fatal: