similar to: doveadm auth cache flush does not work through director

I've got a couple more issues with the doveadm director interface: 1) If I use "doveadm director remove" to disable a host with active users, the director seems to lose track of users mapped to that host. I guess I would expect it to tear down any active sessions by killing the login proxies, like I'd done 'doveadm direct add HOSTNAME 0 && doveadm director flush

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

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

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

Hi, I've been reading doc at http://wiki2.dovecot.org/Director to configure my servers. My question is regarding configuration of doveadm server. I have configured both, director and backend servers, as described in that doc, but I don't know how to run doveadm commands in director servers. doveadm is working, because I can run commands, but they are executed in local (director)

Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or

Hi All, I am running Dovecot 1:2.2.9-1~bpo70+1 on Debian Wheezy. I have just started getting the error below when I do a do a list of proxied users. The list of users appears OK afterwards. # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time . . . My director config is below. Thanks

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

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,

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/"

# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A shows the following message in the log when iterating the 49th user: Oct 17 00:47:17 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- 'e' Oct 17 00:47:17 10.129.3.233 dovecot: doveadm(someuser at example-ll.org):

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"

Our directors hash by domain (director_username_hash = %d), as some of our users share folders with other users of the same domain. We now started using director tags to map domains to their backends. Unfortunately doveadm director map seems no to work with director_username_hash = %d user??? hash??? mail server ip expire time <unknown> 432784257 10.44.88.1?? 2020-11-23 13:10:55

Hi, with the version 2.0.rc3, when I try to remove a mail server from director list, get this error: doveadm director remove 10.180.188.21 (null): doesn't exist but the other commands are working without problem ... doveadm director status mail server ip vhosts users 10.180.188.21 100 2 10.180.188.22

Hi I'm doing: doveadm force-resync -S director1:1234 -A "*" The director gives this error: Jul 06 16:17:29 auth: Error: Trying to iterate users, but userdbs don't support it Jul 06 16:17:29 doveadm: Error: User listing returned failure Jul 06 16:17:29 doveadm: Error: Failed to iterate through some users The director has "iterate_query" set -- Tom

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:

How do you configure an iterate_query SQL lookup for the doveadm director? I tried: service director { ?userdb { ? ... ?} } but userdb is not a valid stanza for director. I do not have a default userdb stanza, all my userdb definitions are specified in service imap/lda/lmtp blocks. Thanks. G H

Hello we are running Dovecot 2.1.9. We have 2 proxies with director and 4 mail servers. We have the user information in a LDAP. I try to do: # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time <unknown>

Am 5/28/2020 um 10:22 AM schrieb Sami Ketola: > >> On 28. May 2020, at 11.12, patosec <patosec at freedaten.at> wrote: >> >> A 'doveadm user -u test at test.com' command on the backend host: >> userdb: test at test.com >> user : test at test.com >> home : /var/spool/imap/test at test.com >> quota : maildir:User quota

> On 28. May 2020, at 11.12, patosec <patosec at freedaten.at> wrote: > > A 'doveadm user -u test at test.com' command on the backend host: > userdb: test at test.com > user : test at test.com > home : /var/spool/imap/test at test.com > quota : maildir:User quota > quota_rule: *:storage=1048576:messages=153000 > > A 'doveadm