similar to: director directing to wrong server (sometimes)

Hi, I have a timeout problem only when I have heavy load in my system. I have two director servers directing to 4 backend servers. The problem is when my smtp relays tries to deliver mail to my users via lmtp (proxied with director). In the smtp logs I have: Jun 12 11:41:18 xenon13 postfix/lmtp[4248]: 4433E5D5A0: to=<myuser at um.es>, relay=pop.um.es[155.54.212.106]:24, delay=31,

Hello, We have two (load balanced) director servers in front of 4 dovecot backend servers. Yesterday we had a problem at backend servers for some users (our SSO was down, so IMAP users couldn't authenticate) and this triggered a problem in director servers where almost nobody could open a new session. In our director's logs I could see errors like this: Mar 20 20:52:47 myotis41

Hello, I know proxy_timeout is the timeout for the director operation. But what is the purpose for proxy_refresh? -- Angel L. Mateo Mart?nez Secci?n de Telem?tica ?rea de Tecnolog?as de la Informaci?n _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337

Hello, I've been using dovecot for a long time, but now I'm having troubles with I change I need to make. I have a director server in front of two backend servers. All of these servers are running dovecot 2.1.16. Redirection to backend servers are based in an attribute of a ldap server. My users are defined in this same ldap server. At this moment, for user authentication we use

Hello, I have configured director in front of dovecot imap/pop/lmtp servers. When I need to manipulate a user mailbox, I use doveadm commands at director server's, with -S option. But some commands return exit code 139 when command returns more than 40 entries (I think). For example, the command: sudo doveadm fetch -u amateo hdr mailbox Trash HEADER Subject "nyctalus11/"

Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:

Hi, I'm having a bit of a problem trying to setup a dovecot proxy. I have a setup with two nodes. One is a working Dovecot/Postfix mail server (node a). The other is running a dovecot proxy and roundcube webmail. Currently I can telnet to port 143 (or openssl s_client to port 993) to localhost on node b. I can then login to a test account on node a. This all works. However, once I instruct

Hi, we are experiencing similar sporadic data timeout issues with dovecot 2.0.20 as in http://dovecot.org/pipermail/dovecot/2011-June/059807.html at least once a week. Some mails get temporarily deferred in the postfix queue since dovecot director lmtp refuses them and the mails are delivered at a later time. The problem applies to mails delivered to single users as well as distribution lists

We have frequent timeout problems after upgrading our imap servers from dovecot 1.1.16 to dovecot 1.2.11. One server acts as proxy only, and the other one is the "real" imap server". The credentials for the proxy service are stored in a remote MYSQL database. There were no trouble with dovecot 1.1.16. But now, with the most recent version, we get frequent login failures. It

Version: 2.1.9 Connecting directly to the proxy server on the LMTP port, issue lhlo, mail from, rcpt to, data. After the . closing of data, it just hangs there. The logs on the proxy server show: Sep 27 19:55:12 proxy1 dovecot: lmtp(9398): Connect from 69.8.2.71 Sep 27 19:55:24 proxy1 dovecot: lmtp(9398): Error: lmtp client: connect(lmtp, 7025) failed: Connection refused root 9398 1102

Hello, i use a proxy only configuration with version 2.2.22 (Ubuntu 16.04) and have now transferred it to version 2.3.10. This works as before. But as soon as i use "auth_cache_verify_password_with_worker = yes", it does not work anymore. The first login still works, but from the second one, where the answer comes from the cache, there is an error. The login is still accepted but

Hi Timo, I'm writing to alert you that even in version 2.1. we have the error: "Can't handle mixed proxy/non-proxy destinations" when we write to two users: one existent and one not. The error occurs randomly. I configure LDAP query in the file : dovecot-ldap.conf in this way: pass_attrs = mail=user,userPassword=password,=proxy=y,mailHost=host, =proxy_timeout=600

Hello, i am delivering Mail from postfix via LMTP to dovecot. I am using the director also for LMTP. As long as i connect to the dovecot LMTP TCP socket from postfix everything is working. postfix main.cf: virtual_transport= lmtp:localhost:30025 But when i try to switch to the local socket postfix main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp The dovecot proxy tries to

Hi, we have a problem with our director proxy configuration. When we run on proxy server the doveadm command with -A switch, fails with the error: # doveadm -D quota get -A doveadm(user1): Debug: auth input: user=user1 proxy starttls=any-cert doveadm(user1): Error: Proxy is missing destination host doveadm: Error: Failed to iterate through some users If we execute the command with a single

Hi, I've been trying to build a password forwarding proxy to Gmail without success... The SSL connection to Dovecot is happening no problem (as far as I can tell), but for some reason the conversation between Dovecot and Gmail is getting timed out. I know this is supposed to be simple... :-( But could somebody please give me some help by pointing what I'm not doing right? No matter

Hi, we get errors about corrupted indexes and we are losing flags with mdbox on NFSv4: Error: Recent flags state corrupted for mailbox Error: Corrupted dbox file Error: Corrupted transaction log file It looks like a LMTP director problem. The user has IMAP IDLE connections open and lmtp delivers to another host. This leads to nfs corruption problems. The user is logged into mail04 and has some

http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root

http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root

Hi, I'm relatively new to Dovecot and I did a bit of search but couldn't find a possible solution for the particular setup I'm working on. Basically I have an SMTP/POP/IMAP proxy setup running Postfix & Dovecot. IMAP/POP authentication is done using the password proxy feature, where the login credentials are passed to the backend server after a db lookup, which does the actual

Hello, I am new to dovecot and I am initially trying to setup a basic imap proxy with password forwarding, I can start the dovecot service, connect and give it my password, and that is where I hang. My config is: root at imap-test:/etc/dovecot# doveconf -n # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-generic x86_64 Ubuntu 12.04 LTS auth_debug = yes auth_verbose = yes debug_log_path =