similar to: lmtp proxy timeout while waiting for reply to DATA reply

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

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, in my dovecot setup the accounting database table shows wrong values which do not correspond with the actual disk space used. The disk usage says 2.6 Gigabytes: mail01:~# du -sh /mail/dovecot/example.org/username 2.6G /mail/dovecot/example.org/username While the doveadm quota get says 7 Gigabytes for the same user: mail01:~# doveadm -f tab quota get -u username at example.org Quota name

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

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, 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, I have discovered a strange behaviour with director proxying... I have a user, its assigned server is 155.54.211.164. The problem is that I don't know why director sent him yesterday to a different server, because my server was up all the time. Moreover, I'm using poolmon in director servers to check availability of final servers and it didn't report any problem with the

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

Hi, After upgrading to dovecot 2.1.12, I see a lot of these errors: # 2.1.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) # Filesystem: ext4 with mdbox storage Dec 10 15:21:04 mail dovecot: imap(user at example.org): Error: Cached message size smaller than expected (5010 < 8192) Dec 10 15:21:04 mail dovecot: imap(user at example.org):

Hi doveadm search -u user at example.org -S localhost:19000 all produces the following error in the logs: dovecot: doveadm: Error: doveadm client attempted non-PLAIN authentication What am I missing? * tcpdump of tcp communication on port 19000 is attached * dovecot.conf is attached Regards Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: dump Type:

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 all, I have a Dovecot setup (2.1, I will switch to 2.2 soon) with one Director and 2 backend servers. When my MX server (Postfix) tries to deliver mail to Dovecot via LMTP, it often gets an error "451 4.4.0 Remote server not answering (timeout while waiting for reply to DATA reply)" from the Director. Service LMTP is configured with "client_limit = 1" on Director en

I'm trying to install postfix-2.0.16-14.RHEL on a newly installed CentOS 3.3 boxen and I get the following error: Preparing... ########################################### [100%] 1:postfix ########################################### [100%] link /usr/share/man/man8/sendmail.8.gz incorrect for slave mta-sendmailman (/usr/share/man/man1/sendmail.1.gz

Hello I have a problem with lmtp delivery to usernames with '-' char. Everythong after - is ignored. when delivering to test-test2 the error message is. User doesn't exist: test I suspect this is a sideefect of auth_username_format = %Lu I have tried %Ln without success. Imap works without problems for those users. How can I disable this mapping for lmtp and use verbatim

I just configured postfix' virtual_transport to point at my dovecot director, but am seeing occational problems like this: Aug 31 11:50:06 smtpgw postfix/lmtp[5339]: 69E2F5410D: to=<email at example.net>, relay=loadbalancers.example.net[192.168.42.17]:24, delay=0.15, delays=0.14/0.01/0/0, dsn=5.5.4, status=bounced (host loadbalancers.example.net[192.168.42.17] said: 501 5.5.4 Invalid

* Ralf Hildebrandt <r at sys4.de>: > > I updated dovecot today and all over a sudden I'm getting: Old: dovecot-lmtpd:amd64 2:2.2.15-1~auto+136 New: dovecot-lmtpd:amd64 2:2.2.15-1~auto+148 >From Stephan Bosch's repos. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263

Am 06.03.2015 um 14:44 schrieb Ralf Hildebrandt: > I updated dovecot today and all over a sudden I'm getting: > > Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], > delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 >

* Reindl Harald <dovecot at dovecot.org>: > lmtp_destination_concurrency_limit on postfix side It's not a postfix issue. postfix is merely reporting what Dovecot said. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer

Op 16/08/2018 om 12:01 schreef Stephan Bosch: > I have a theory. Will try something later today. Yes, I can reproduce the problem. I am working on a fix. Regards, Stephan.