similar to: No failover from director to backend?

Hi @all, on Saturday I upgraded two dovecot servers from squeeze to wheezy and dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade everything worked fine at first. On Sunday Morning I recognized these errors (they occured after a reload for logging purpose on midnight) on one server: director: Error: Ring SYNC appears to have got lost, resending After reloading/restarting

I haven't done this on the old, working machine. So there must be a difference between Debian 7 and 9 how open files are handled? Regards Patrick Aki Tuomi schrieb: > You probably need to increase ulimit -n > > Aki > > > On 23.08.2017 14:10, Patrick Westenberg wrote: >> Hi @all, >> >> after re-installing one of my two frontends/proxy-servers I get

Hi @all, after re-installing one of my two frontends/proxy-servers I get the following error messages after some time (sometimes after 1h, sometimes after 24h): 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:55 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error: socketpair() failed: Too many open files 11:23:56 imap-login: Error:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a dual stack server with Dovecot 2.1.10 listening on v4 and v6 Dovecot has a Comodo SSL certificate issued via NameCheap that works as expected with IPv4 in 10-ssl.conf I have enabled these configuraction directives: ssl = yes ssl_cert = < /path/to/file.crt ssl_key = < /path/to/file.key ssl_parameters_regenerate = 202 hours If I

Hi all, I just recognized a lot of log entries like this on my proxy: Dec 03 13:50:54 imap-login: Info: proxy(mail at example.com): disconnecting 1.2.3.4 (Disconnected by server): user=<mail at example.com>, method=PLAIN, rip=1.2.3.4, lip=2.4.6.8, TLS, session=<qk02v6DsJwBTlUQX> There are no similar entries on the backends. What does this mean? Something I have to worry about?

Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection

Hello, are you using systemd? May be you have to edit unit-file for dovecotservice and increase filelimit LimitNOFILE=infinity Hajo Am 23.08.2017 um 14:21 schrieb Patrick Westenberg: > I haven't done this on the old, working machine. > > So there must be a difference between Debian 7 and 9 how open files are > handled? > > Regards > Patrick > > > > Aki

You probably need to increase ulimit -n Aki On 23.08.2017 14:10, Patrick Westenberg wrote: > Hi @all, > > after re-installing one of my two frontends/proxy-servers I get the > following error messages after some time (sometimes after 1h, sometimes > after 24h): > > > 11:23:55 imap-login: Error: socketpair() failed: Too many open files > 11:23:55 imap-login: Error:

Hi @all, I have a 3 server setup (MX ==LMTP==> Proxy ==LMTP==> Backend). After upgrading to 2.2.18 I was able to use LMTPs from MX to the proxy but not from the proxy to the backend: Received: from mf01.example.net ([172.17.1.5]) by mb01.example.net (Dovecot) with LMTP id T+LnDWrvcVWDSwAAJnBBGg for <patrick at example.net>; Fri, 05 Jun 2015 20:50:58 +0200 Received: from

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP

Hi, First, my version: [root at centos1 conf.d]# dovecot --version 2.2.15 [root at centos1 conf.d]# I have already configured dovecot that way (on one single VM, so everythinh is stored on the same machine) - A post fix server sending out to LMTP - LMTP is the dovecot LMTP server, configured with "lmtp-proxy= no", - LMTP checks the users receiving

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12

In data marted? 11 settembre 2018 10:46:30 CEST, Timo Sirainen ha scritto: > On 11 Sep 2018, at 10.57, Simone Lazzaris <s.lazzaris at interactive.eu> wrote: > > Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file > > doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion > > failed: (conn->to_ring_sync_abort == NULL) Sep 11 03:25:55 imap-front4

I'm working the kinks of a new director based setup for the eventual migration away from courier. At this point, with everything basically working I'm trying to ensure that things are properly monitored and I've run into an issue. There doesn't appear to be a way to get dovecot to tell if it is (or is not) connected and properly synced with the other director servers in the ring

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The

I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: "Warning: Locking transaction log file xxxx/indexes/dovecot.list.index.log took 60 seconds (syncing)" It's just an empty mailbox. Is there any way to do a login test, without locking the index files? Hence

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at interactive.eu> > > wrote: > > > > > > The only suspect thing is this: > > > > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host > > 192.168.1.142 > > vhost count changed from 100 to 0 >

Hi everyone, some days ago I had trouble with my NFS-Server (high delays) which caused dovecot lmtp to deliver the same message several times (up to 10x). I recognized some old/unused .nfsXXXX files in the maildirs which seemed to be index files. I deleted them and everything was fine again. However, there are still 2-3 mailboxen where mails (old and new ones) are delivered multiple times. All

In data venerd? 7 settembre 2018 11:20:49 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.25, Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > > Actually, I have a poolmon script running that should drop vhost count for > > unresponsive backends; the strage thing is, the backends are NOT > > unresponsive, they are working as ususal. > If it's this

Hi, I've been running dovecot for many years, but now i've hit a strange problem. when retrieving imap there is sometimes in 1 of 4 imap requests a 4sec latency. * notes: - connected directly to the backends this latency disappears - removing a director from the loadbalancer(lvs) so i'm the only connected to the director this latency disappears too I would appreciate some feedback