similar to: Wrong protocol in socket (director-doveadm vs director) ?

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

Couple questions about running doveadm with multiple instances... I have Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and main instance running. When I try to lookup something on the main instance (which is handling user auth) via its auth-userdb socket directly, I get an error: # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser doveadm(root): Error: passdb

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically

I'm trying to follow the instructions for configuring Dovecot LMTP with postfix for virtual domains but whenever mail arrives, in /var/log/maillog, I see Sep 23 16:01:20 mybox postfix/pipe[572]: 999C83206C6: to=< user at mytest.domain.com>, relay=dovecot, delay=0.08, delays=0.04/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: pipe: fatal: pipe_command: execvp

We have a few dovecot servers all pointing to the same mail location (an NFS mount on a NAS drive). This could lead to a possible bottleneck eventually and we were wondering if it's possible to have dovecot direct x number of users to one message store location while others get their mail on a different mount?

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, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

I was reading "conf.d/10-director.conf" and it mentions Dovecot proxy. I've been using perdition in the past for my pop/imap proxying needs and wasn't sure if Director could also use perdition or if it only works with Dovecots proxying. Thanks!

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 all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting):

I have a folder created in dovecot entered by the user as "??o??" On the file system it appears as "&APEA8Q-o&AOkA6Q-" (mUTF7) When creating a sieve rule, to file into the folder ??o??, I am converting the name from UTF8 into UTF7, the rule becomes require ["fileinto"]; if header :contains ["From"] "user at domain.com" { fileinto

Something I noticed on a 2.1.7 director test cluster (two directors, three backends): 'doveadm proxy kick user' will kick all connections for that user on that director only. Any additional connections on other directors will remain active unless the command is run on all directors. Are the proxy and director sub-commands intended to be separate and distinct in their operation? If so,

I'm trying to configure my proxy/director server, which proxies imap/pop/managesieve correctly already, to proxy LMTP to my backend message store server (dovecot+postfix already configured there) This is what I have so far: 10-auth.conf using auth-static.conf.ext instead of auth-ldap.conf.ext (switching to this made proxying imap/pop/managesieve work) 10-director.conf protocol lmtp {

I have successfully set up the master user on the destination server (2.0.11) and tests have worked. now I'm working on the proxy Before I had the proxy just forward everything to the backend and had the destination server do the authentication. My authentication is done via LDAP but not really sure how to append the master user and password to the users credentials after authentication is

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

I'm trying to configure a doveadm service that will proxy trough our directors, following the recipie at: http://wiki2.dovecot.org/Director#Doveadm_server So on the backends I have: service doveadm { inet_listener { port = 24245 address = * } } doveadm_proxy_port = 24245 local 192.168.42.0/24 { doveadm_password = suPerSeecret } I assume the "local"

Hi, I have a director farm running in front of dovecot pop/imap servers. For a reason, one of my backend servers have been down, so poolmon disables it in director servers and users corresponding to it has been sent to other servers. Until this, no problem. Now my failed backend server is up again, and I want to redirect all of its users to it, without waiting for it director sessions to

I'm trying to compile the source for Dovecot 2.0.2 on a Solaris 10 SPARC machine. > uname -a SunOS ommtca013 5.10 Generic_138888-07 sun4v sparc SUNW,Sun-Blade-T6300 Solaris > cat /etc/release Solaris 10 10/08 s10s_u6wos_07b SPARC I've installed the following binaries from sunfreeware for dovecot 1.1 to use with 2.0.2 gcc-3.4.6-sol10-sparc-local

Hi I started migrations dovecot cluster from 2.2.36.4 (debian) to 2.3.8 (cetos8) .I read https://wiki2.dovecot.org/Upgrading/2.3 In 10-director.conf I must disable director_doveadm_port like: #director_doveadm_port = 2424 and add: ..... service doveadm { ? inet_listener { ??? port = 2424 ? } } Is this correct ? the rest of the contents of the file service director { ? unix_listener