search for: director_servers

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 } fifo_listener login/proxy-notify { m...

...ovecot is always trying to start Director service and I couldn't find a way to stop Dovecot from giving out errors. 1. When the entire Director configuration block is commented out, there errors: dovecot: director: Fatal: No inet_listeners defined for director service (for standalone keep director_servers empty) dovecot: master: Error: service(director): command startup failed, throttling for 2 secs 2. When the director_servers line is configured as "*director_servers = *", there errors: dovecot: director: Error: Empty server list dovecot: director: Fatal: Invalid value for director_mai...

...posed to work. Ah, the information comes from the other director running. The other one is using an unpatched version of dovecot. If I shutdown the other director instance, it seems to work. Tomorrow I'll do more testing. Good work, thank you. BTW: I've put there an IPv6 address into the director_servers list (not an DNS name). director_servers = 2001:x:y:f33::5:1 ? inet_listener { address = :: port = 9090 } it doesn't recognize itself: Oct 14 01:06:13 director1 dovecot: director: Fatal: director_servers doesn't list ourself director_servers = 2001:x...

...fourth instance on each front end server for the director process. Currently we just return the backend server ip via SQL and use the old master username/password to proxy the inbound POP/IMAP sessions to the correct backend server. The plan is for each instance to have connect to the same list of director_servers (one from each front end server). What's the trick to separate a director instance into its own setup and having multiple instances/servers connect to that director? Currently I have on my proxy instance: director_servers = 10.128.1.42:9090 (this is the inet_listener from the director i...

...rector/dovecot.conf -n # 2.0.14: /etc/dovecot-director/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot-director/ director_mail_servers = 101.180.245.101 director_servers = 101.180.245.101 disable_plaintext_auth = no lmtp_proxy = yes mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl mail_uid = 5000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-c...

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

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...

...thing *too* obvious... Here's doveconf -n from imapdir1: # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.7 (Tikanga) base_dir = /var/run/dovecot/ director_mail_servers = penguina.uvm.edu penguinb.uvm.edu penguinc.uvm.edu director_servers = imapdir1.uvm.edu imapdir2.uvm.edu lmtp_proxy = yes login_trusted_networks = 132.198.101.211,132.198.101.212,132.198.101.213,132.198.101.214,132.198.101.215,132.198.101.216,132.198.100.45,132.198.100.46,132.198.100.47 passdb { args = proxy=y nopassword=y protocol=smtp driver = static }...

...??? mail server ip expire time # doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 auth_cache_size = 32 M auth_cache_ttl = 2 hours auth_debug = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /var/run/dovecot/ director_mail_servers = x.x.x.x director_servers = y.y.y.y disable_plaintext_auth = no mail_debug = yes passdb { ? args = nopassword=y proxy=y ? driver = static } service director { ? fifo_listener login/proxy-notify { ??? mode = 0666 ??? user = $default_login_user ? } ? inet_listener { ??? port = 9090 ? } ? unix_listener director-userdb { ??? mo...

...e 88 (login_host_callback): assertion failed: (strncmp(request->line, "OK\t", 3) == 0) Any ideas? Patrick node1: # 2.2.5: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 auth_mechanisms = plain login director_mail_servers = 172.17.1.2 172.17.1.1 director_servers = 172.17.1.3 172.17.1.4 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy i...

...handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:22:33 retr01 dovecot: pop3-login: Error: Timeout waiting for handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:22:33 retr01 dovecot: director: Fatal: No inet_listeners defined for director service (for standalone keep director_servers empty) Jun 3 16:22:33 retr01 dovecot: master: Error: service(director): command startup failed, throttling Jun 3 16:23:08 retr01 dovecot: pop3-login: Error: Timeout waiting for handshake from auth server. my pid=32152, input bytes=0 Jun 3 16:23:33 retr01 dovecot: pop3-login: Disconnected: Inacti...

...Is there any chance that this will make it into Dovecot's next release? BTW: The ambiguity of 2001:db8::9090 remains. Shouldn't you allow [2001:db8::]? resp [2001:db8::9090]? resp. [2001:db8::]:9090? for such cases? (In case one want's to use IPv6 addresses instead of hostnames in the director_servers option. (And probably in other places too.)) ?) Address ?) Address:Port Best regards from Dresden/Germany Viele Gr??e aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49...

...y - 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 for the following setting... *director_servers = mailproxy.internal* I have created a Lambda to continually update the values for the A records found in the *.internal* zone since EC2 instances can come and go for a variety of reasons. If those values changes will the Director service "notice" or will a "service dovecot restart...

I noticed 2 minor things with the director. 1) if I start 2 directors, but in 1 of them I dont add the other as a director_servers, they both start spamming the logfiles really really fast. It seems there is no backoff mechanism in the protocol between directors. 2) user mail server ip expire time cor 194.109.26.171 2010-09-02 14:32:13 <unknown>...

...director tries to use the same port it is listening on when making backend connections. If I point it to the local backend server, it tries to connect to itself which fails. Is there a way to specify the backend ports that director tries to connect to? I see there is a way to specify the port in director_servers but I'm not sure how I would specify the different ports for the different backend services, if this is even possible.

...ector to redirect these users to the remaining backend. Am I wrong or is the director not working as expected? Regards Patrick # 2.1.6: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.3 172.17.1.4 lmtp_proxy = yes log_path = /var/log/dovecot.log managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify...

...s don't occur on my old machine (Debian 7). Any ideas? Regards Patrick # 2.2.32.rc2 (a350120ca): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.4.67-1-pve x86_64 Debian 9.1 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.32 172.17.1.3 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy in...

...>> >> >> >> # 2.2.32.rc2 (a350120ca): /usr/local/etc/dovecot/dovecot.conf >> # Pigeonhole version 0.4.19 (e5c7051) >> # OS: Linux 4.4.67-1-pve x86_64 Debian 9.1 >> auth_mechanisms = plain login >> director_mail_servers = 172.17.1.1 172.17.1.2 >> director_servers = 172.17.1.32 172.17.1.3 >> director_user_expire = 5 mins >> lmtp_proxy = yes >> log_path = /var/log/dovecot.log >> managesieve_notify_capability = mailto >> managesieve_sieve_capability = fileinto reject envelope >> encoded-character vacation subaddress comparat...

..._cache_verify_password_with_worker = yes auth_mechanisms = plain login auth_verbose = yes debug_log_path = /dev/stdout default_client_limit = 10400 default_process_limit = 1024 default_vsz_limit = 1 G deliver_log_format = msgid=%m: %s %{session_time} %$ director_mail_servers = 10.10.10.2 10.10.10.3 director_servers = 10.10.1.2 10.10.1.3 imap_id_log = * imap_max_line_length = 2 M import_environment = TZ CORE_OUTOFMEM CORE_ERROR info_log_path = /dev/stdout instance_name = dovecot_director listen = 10.10.1.3,:: lmtp_proxy = yes log_path = /dev/stderr log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_forma...

...auth_verbose = yes auth_verbose_passwords = plain auth_worker_max_count = 50 base_dir = /var/run/dovecot/ default_login_user = nobody director_doveadm_port = 9091 director_mail_servers = 192.168.1.142 192.168.1.143 192.168.1.144 192.168.1.145 192.168.1.216 192.168.1.217 192.168.1.218 192.168.1.219 director_servers = 212.183.164.157 212.183.164.158 212.183.164.159 212.183.164.160 listen = * passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener di...