similar to: director / main instance

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

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"

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

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 all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the

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

hello! Is "doveadm director map" command suppose to work when I store "host" value in mysql table? It gives me nothing in output with no errors in log. I've successfully setup directors with static passdb, and decided to give a try setup with storing host value in mysql table. The proxying is actually working, I'm just unhappy with no output from "doveadm

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

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

Hi would it be possible to consider a new parameter for replication: doveadm_local_ip which allows the source ip address to be set when connection to a remote dovecot for replication? It could be useful when the network interface has multiple ips and a specific one is used for mail services. See attached proposal. I tested against 2.2.36 only. It applies correctly against 2.3.4 with a warning,.

Hello All, Have anyone met the problem I am struggling with at the moment ? The problem is when I run two instances of dovecot 2.1.8 which are one for proxy-director and another one is a regular one on the same server then I have big amount of strange entries in the /var/log/mail.err: Jul 26 11:51:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:51:20 dovecot-test-1

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:

Hello all, today I got this crash from dovecot (2.0.14) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa)? [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6)

Hello all, why I can run whis command: imap1:~ # doveadm user user001 userdb: user001 ? mail????? : maildir:/var/maildir/vol04/4/46/user001 ? home????? : /var/mailfilter/vol04/4/46/user001 ? quota_rule: *:bytes=100000000 but not this one: imap1:~ # doveadm quota get -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed doveadm(user001): Fatal: passdb lookup failed what

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

Hi All, I have compared Dovecot performance to Courier and it appears that as a POP3 server Dovecot is slower in 2 times but as an IMAP server it is faster in 1.5 times. The same node (16CPUs), testing time is 30 min, please see results and dovecot configs attached. Benchmark software is MStone used by Sendmail Inc so is is quite reliable. I do not see anything else to tweak in Dovecot to

Hi, we are running a 4 host setup which each hosts a director+mailbox which is mounted via NFSv4 from a DRBD cluster. * Dovecot upstream release 2.1.16 * Doveadm batch subcommand fix - http://hg.dovecot.org/dovecot-2.1/raw-rev/850b5d8bbcc9 * Pigeonhole release 0.3.4 Now we would like to remove duplicate Mails using the vnd.dovecot.duplicate extension using a SIEVE script like this: require

Hi, we are running a cluster using mdbox on NFS with director+mailbox on each node. After running our daily doveadm purge loop over all users, we got dbox corruption... doveadm user "*" |\ while read username do doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -u "$username" done For one user (which deleted a lot of messages from his mailboxes today), we

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr