similar to: Dot Lock timestmap, users disconnections from roundcube

Hello We are using SLAMD (Distributed Load Generation Engine, www.slamd.com) to benchmark our dovecot server (ldap auth). We are simulating 2.000 simultaneous logins and 20% of them fail. We saw the following errors in the log: Apr 12 09:40:07 buzon dovecot: auth: Error: ldap(correo,192.168.4.153): Request queue is full (oldest added 1 secs ago) Apr 12 09:40:07 buzon dovecot: auth: Error:

I have seen some strange error log messages in our dovecot server (2.0.15, RHEL 5.7x64, mdbox+zlib, local storage, high load) Dec 14 22:01:27 buzon dovecot: imap(fmcarrasco): Error: /indices_dovecot/indices/07/47/fmcarrasco/mailboxes/INBOX/dovecot.index reset, view is now inconsistent Dec 14 22:00:27 buzon dovecot: imap(cfp): Error:

??? We have upgraded today from Dovecot 2.2.31 to Dovecot 2.2.33.2 and modified our config to include ITERINDEX in mail_location and we are detecting some errors like this: /Dec 13 08:17:31 buzon_rhel7 dovecot: imap(rboloix): Error: stat(/buzones/location/18/48/rboloix/mailboxes/SIT - Pra&AwE-cticas 2014/dbox-Mails) failed: No such file or directory// //Dec 13 08:40:24 buzon_rhel7

Hello In my setup I have the following in dovecot.conf (dovecot 2.0.12) mail_home = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/ mail_location = mdbox:/buzones/my_domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n My problem is with the autocreation of mail_home. We are using roundcube+sieve plugin and the first time a user tries to use sieve fails with

I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via telnet to 110 port of the dovecot server the client hangs: telnet 192.168.4.80 110 Trying 192.168.4.80... /Connected to 192.168.4.80. Escape character is '^]'./ In syslog I got the following error: /Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login) in directory / failed: Permission denied

Hello. I have tried to restore a test user mailbox and I get a segmentation fault doveadm -D import -u ox101 at us.es mdbox:/backup/bacula-restores/buzones/mysite/15/b1/ox101/ "" all /doveadm(entrega): Debug: Loading modules from directory: /usr/lib64/dovecot doveadm(entrega): Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so doveadm(entrega): Debug: Module

On 16.10.2017 13:30, Mar?a Arrea wrote: > El 16/10/17 a las 12:25, Aki Tuomi escribi?: >> ITERINDEX is a flag, it's not supposed to have any value. >> >> Aki > So ITERINDEX=yes should be the right value? This is the right > mail_location settings? > >

ITERINDEX is a flag, it's not supposed to have any value. Aki On 16.10.2017 13:22, Mar?a Arrea wrote: > > ??? I have tested putting the same value in ITERINDEX & INDEX, is this > the expected? > > ??? Regards > > ??? Mar?a > > El 07/09/17 a las 08:44, Mar?a Arrea escribi?: >> Hello >> >> ??? I have a question about the new setting ITERINDEX.

Hello I have a question about the new setting ITERINDEX. This is my filesystem layout /indices_dovecot : 8 x Fast SSD drives /buzones : 32x SAS 10k rpm disks /buzones/alternativo : 24 x SAS 7.2k rpm slow disks This is my mail_location: mail_location =

If you are using systemd, you might want to create /etc/systemd/system/service.dovecot.d/override.conf with ProtectSystem=no if you want writable /etc directory. > On 28 November 2018 at 18:49 Maria Arrea <maria-arrea at gmx.com> wrote: > > > Since I upgraded to 2.3.4 I have lots of line in logs like these: > > Nov 28 17:35:48 buzalum_rhel7 dovecot: imap(iniramgon

Hello I have found this entries in my log /var/log/maillog.13.xz:Jun 6 17:03:26 buzon dovecot: imap(juanan): Error: mdbox /buzones//18/66/juanan/mailboxes/P7.Bielorrusia/cd-eslpod-enviado/dbox-Mails: Storage keeps breaking /var/log/maillog.108.xz:Mar 4 01:42:09 buzon dovecot: imap(lbandera): Error: mdbox /buzones/0b/11/lbandera/mailboxes/Sent/dbox-Mails: Storage keeps breaking

Thank you Mr. Aki ??? Should this info about ITERINDEX be present in https://wiki.dovecot.org/MailLocation ? Bit confusing now. El 16/10/17 a las 12:35, Aki Tuomi escribi?: > > On 16.10.2017 13:30, Mar?a Arrea wrote: >> El 16/10/17 a las 12:25, Aki Tuomi escribi?: >>> ITERINDEX is a flag, it's not supposed to have any value. >>> >>> Aki >> So

El 16/10/17 a las 12:25, Aki Tuomi escribi?: > ITERINDEX is a flag, it's not supposed to have any value. > > Aki So ITERINDEX=yes should be the right value? This is the right mail_location settings? mail_location=mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:ITERINDEX=yes:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n > >

??? I have tested putting the same value in ITERINDEX & INDEX, is this the expected? ??? Regards ??? Mar?a El 07/09/17 a las 08:44, Mar?a Arrea escribi?: > Hello > > ??? I have a question about the new setting ITERINDEX. This is my > filesystem layout > > ??? /indices_dovecot : 8 x Fast SSD drives > ??? /buzones : 32x SAS 10k rpm disks > ??? /buzones/alternativo

Hello. We are using mdbox 2.013 + zlib, without SIS. When I try doveadm force-resync on a user's mailbox I get the following: doveadm(jmraya): Error: Corrupted dbox file /buzones/mydomain/0b/59/jmraya/storage/m.27 (around offset=22805024): Unexpected EOF while reading metadata header doveadm(jmraya): Warning: dbox: Copy of the broken file saved to

Hello I am starting testing with dovecot 2.0.9. In my //etc/dovecot/dovecot.conf/ I have the following line: /mail_location = mdbox:/mydomain.org/%2.26Hn/%2.200Hn/%n:INDEX=/mydomain.org/indexes/%2.26Hn/%2.200Hn/%n/ These are my questions (a long mail): *1? How should I restore from backup with mdbox & separate indexes?* I have read in dovecot list archive about restoring the full

Hello everyone, We have Dovecot 2.1.6. With different Namespaces: ... mail_location = maildir:%h/Maildir ... namespace { separator = . prefix = inbox = yes type = private } namespace { inbox = no location = prefix = INBOX. separator = . hidden = yes type = private list = no } namespace { location = maildir:/buzon/archivo/%u/_ARCHIVO prefix = _ARCHIVO. hidden = yes