similar to: minor director issues

Hi all, anyone having any problems with restarting the director? Every time I bring down 1 of the director servers, reboot it, or just restart it for whatever reason, im seeing all kinds of problems. Dovecot generally always gives me this error: Jan 20 22:49:55 imapdirector3 dovecot: director: Error: Director 194.109.26.173:444/right disconnected before handshake finished It seems the directors

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

Hi, I'm setting up an IMAP/POP cluster using dovecot director for some NFS reasons and I'm getting some troubles with director_servers directive. Configuration is shared on both nodes : director_servers = 10.0.50.50 10.0.50.51 director_mail_servers = 192.168.0.150 192.168.0.151 director_user_expire = 15 min service director { unix_listener login/director { mode = 0666 }

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

I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet

hi, I wrote a patch to openssh sshd.c which enables "exponential backoff", so that an attacker cannot brute force your password by making hundreds of login attempts. here is the code: http://sam.nipl.net/sshd-backoff/ An attacker who fails to login is locked out (by IP address) for 1 minute, and the lockout period doubles for each failed login after that. Normally three logins are

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

I plan on putting two dovecot directors in front of our backend dovecot pop/imap servers, instead of our current haproxy loadbalancing of the connections -- but how do we handle SSL in such a setup. Will all SSL be terminated on the directors automatically, and then proxyed plain text, or is there any configuration needed to achieve this ? Does it matter that the directors are v2.0 while the

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

Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from

Hi All, Does anyone know how to disable the Director service. In our current running Dovecot 2.2.4, if the director configuration is commented out and Dovecot has no errors nor warnings. But the version 2.2.12 I'm testing with gives out fatal errors. We have dedicated Dovecot Director servers that serve the public frontend and separate dedicated imap/pop3 servers on the backend

The sample Director configuration (10-director.conf) says that director_servers and director_mail_servers can be lists of either IPs or hostnames: # List of IPs or hostnames to all director servers, including ourself. # Ports can be specified as ip:port. The default port is the same as # what director service's inet_listener is using. #director_servers = # List of IPs or hostnames to all

I'm accustomed to systems where even the first failed login attempt incurs a 5 second delay. I don't think that's too harsh, but everyone has their own needs and considerations. This could be made configurable. -Jay -----Original Message----- From: Rick Jones [mailto:rick.jones2 at hp.com] Sent: Wednesday, December 15, 2004 8:09 PM To: Jay Libove Cc: openssh-unix-dev at

Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 00:10:50 CEST): > Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 23:49:20 CEST): > ? > > > > Proxying in general does check that hostname matches the SSL certificate, because both the hostname and IP address are sent to login process. So it should work in a way that host=<hostname> and

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director

Hi Timo Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 01:10:20 CEST): ? > Ah, the information comes from the other director running. The other one > is using an unpatched version of dovecot. Your patch for backend-certificate verification works. Thank you for the good and fast work. Is there any chance that this will make it into Dovecot's next release? BTW: The

Hello, I am currently running 2.2.31. I have a cluster of dovecot instances running in AWS. - Two instances running Director/Proxy - Two instances running Dovecot. -- Storage for the Dovecot instances is EFS. My setup works, requests for 143 hit my Director cluster and are proxied to an appropriate dovecot backend. My question is how often if at all the Director service looks up the addresses

Dear Samba Group, I recently updates our samba addc's to 4.18.6 (from 4.7.7). We use roaming profile and a login script which queries active shares and printers on the logon servers. Since the update i see a lot of rpcd_winreg processes if an user logs on. It are around 40 of these processes each consuming around 60MB. The servers have 1-2GB of ram assigned so they start swapping everytime an

As recommended by Volker Lendecke I added the option. rpcd_winreg:idle_seconds = 5 Now on 2GB Servers swapping is avoided and on 1Gb Servers the server goes back to normal in ~5 seconds after the logon process has finished. Am 10.10.2023 um 13:58 schrieb Achim Gottinger via samba: > Dear Samba Group, > > I recently updates our samba addc's to 4.18.6 (from 4.7.7). We use roaming

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