similar to: dsync dovecot / Failed connection refused

Displaying 20 results from an estimated 10000 matches similar to: "dsync dovecot / Failed connection refused"

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 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 06
2
Dovecot dsync 'ssl_client_ca'
Hi Aki, I do not have any error message but (on both server): doveadm replicator status '*' doveadm(root): Fatal: net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Connection refused Thx Le vendredi 3 f?vrier 2017 ? 17:09:52, vous ?criviez : > Please keep responses in list. rm -f > /var/lib/dovecot/ssl-parameters.dat, i think it was in that dir. > On
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 =
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:
2017 Jan 24
0
dsync dovecot / Failed connection refused
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 05:58 PM, Thierry wrote: > 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
2019 Oct 18
3
[2.3.8] possible replication issue
Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see
2014 Sep 09
1
My Dsync isn't replicating 'EXPUNGE' IMAP command
Hi! I have two Dovecot-2.2.13 servers with Dsync Replication: server1 and server2. When I execute 'EXPUNGE' on server1 side, the messages with FLAG \Deleted are expunged only on server1. The message is still present in Server2. Could someone give me a hint reason for this ? Thanks in advance! -- Thiago Henrique ======================================================================
2013 Oct 30
1
Replication on v2.2.6 - I'm stuck (again)
Hi, I'm trying to get Dovecot replication working between two servers. I didn't have much luck on v2.1.3, so after receiving advice from the list I have upgraded to v2.2.6. I now get the error: Oct 30 11:50:16 server1 dovecot: doveadm(mark): Error: user mark: Auth PASS lookup failed Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync: /var/run/dovecot/auth-userdb: passdb lookup
2019 Dec 05
2
[2.3.8] possible replication issue
I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > upgrading to 2.3.9
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
2020 Jun 18
1
Sieve-scripts won't replicate
Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won?t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won?t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The
2014 Jan 30
1
Is replication broken?
Hi, Apologies for this being my 248th post about replication... The current error I'm getting is: Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync( Server2.test.com): read() failed: read((fd)) failed: Connection reset by peer Subsequent errors are: Jan 30 12:15:47 Server1 dovecot: dsync-local(MailUser1): Error: read( Server2.test.com) failed: EOF The above error is
2014 Jan 13
1
Replication and public namespaces
Hi, I'm having some issues with replicating public namespaces. Everything seems to work fine for private namespaces, but while importing some huge mailboxes (many small mails) into a public namespace via imapsync, something goes wrong. The expected mail flow is: old-server (imapsync)> new-server1 (replication)> new-server2 But then, dovecot seems to run into race conditions when the
2017 Feb 06
0
Dovecot dsync 'ssl_client_ca'
Dear Thierry, - Have you checked that port 12345 as specified below is open/forwarded and actually /used/ by dovecot (e.g., use "netstat -tulpn|grep dovecot")? - Did you retrace your steps and have you verified that synchronisation works with ssl disabled? - Did you verify your certificate files (e.g., "openssl verify -verbose -CAfile /etc/ssl/certs/GandiCA2.pem
2017 Feb 03
0
Dovecot dsync 'ssl_client_ca'
Please keep responses in list. rm -f /var/lib/dovecot/ssl-parameters.dat, i think it was in that dir. On 2017-02-03 17:00, Thierry wrote: > Hi, > > I have removed the '<' : > > ssl_client_ca_file = /etc/ssl/certs/GandiCA2.pem > > But now: > > doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 > doveadm:
2017 Feb 27
1
Fwd: Some mails do not get replicated anymore after memory-exhaust
Hey guys, overall I have an working dovecot replication between 2 servers running on amazon cloud. Sadly I had some messages that my server ran out of memory. After investigating a little bit further I realized that some mails didn't got replicated, but I'm not sure if this was related to the memory exhaust. I was expecting that the full-sync would catch them up but sadly it's not.
2016 Sep 01
2
Dsync config help
I was able to workaround the ?Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don?t support credentials lookups (to see if user is proxied, because doveadm_port is set)? problem:? => I simply disabled ?doveadm_port? and added the port number at the end of the remote URL in ?mail_replica? Replication seems to work although I have regular errors (idk if they are related to each
2017 Jan 04
3
Dovecot dsync tcps sends incomplete certificate chain
Hi, I'm trying to configure a Dovecot dsync service between two servers, using a tcp+ssl connection and a valid Let's Encrypt certificate. I followed the guide on the wiki (http://wiki.dovecot.org/Replication) using the tcps method, but when I launch the replication it fails writing on the log (/var/log/mail.err): (Server 1 - sync "client" )| Error: sync: Disconnected from
2017 Feb 07
2
Dovecot dsync 'ssl_client_ca'
Bonjour Markus, > - Have you checked that port 12345 as specified below is open/forwarded > and actually /used/ by dovecot (e.g., use "netstat -tulpn|grep dovecot")? Yes of course: tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN 22025/dovecot tcp6 0 0 :::12345 :::* LISTEN 22025/dovecot > -