similar to: doveadm director proxy

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

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

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

We have a checkpassword authentication with mysql pre-fetch for the userdb lookups. When trying to do: doveadm search -u andytest at xecu.net mailbox Trash DELETED I get: doveadm(andytest at xecu.net): Error: user andytest at xecu.net: Auth PASS lookup failed doveadm(andytest at xecu.net): Fatal: /var/run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because

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

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 have directors and backend servers running on the same systems (x3). To be able to run doveadm foo with a minimum of fuss (without having to list socket paths explicitly), should it be the director that's the "default"? If so, is it safe to symlink '/var/run/dovecot' to '/var/run/dovecot-director', or should I just make the director's base path /var/run/dovecot

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)

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

Hello, I'm testing passdb auth binds with dovecot 2.0.16, but for some reason dovedm fails to work with the configuration showed below. The network trace shows the successful bind for the administrative user (uid=mailapp), but nothing for the mail user (uid=user001). what am i missing here? # doveadm mailbox list -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed

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

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the

I've had 2x director ring up and running with production load on 2.1.8 with around 10,000 active connections for two weeks and everything has been working great - until this morning. There isn't anything obvious in the logs beyond the fact that the director connections started bouncing. It was not resolved by reloads or restarts or an upgrade to 2.1.9 (only the directors.) I've

We upgraded our two dovecot directors from v2.0.14 to dovecot-ee 2.1.10.3 this week, and after that mail seems to be flowing a lot slower than before. The backend mailstores are untouched, on v2.0.14 still. After the upgrade we've been hitting process_limit for lmtp a lot, and we're struggeling with large queues in the incoming mailservers that are using LMTP virtual transport towards our

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

http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz.sig + doveadm altmove: Added -r parameter to move mails back to primary storage. - v2.0.14: Index reading could have eaten a lot of memory in some situations - doveadm index no longer affects future caching decisions - mbox: Fixed crash during mail delivery when mailbox didn't

http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz.sig + doveadm altmove: Added -r parameter to move mails back to primary storage. - v2.0.14: Index reading could have eaten a lot of memory in some situations - doveadm index no longer affects future caching decisions - mbox: Fixed crash during mail delivery when mailbox didn't

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