similar to: v2.2.32 released

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.

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

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 =

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

Timo Sirainen wrote: > There are various changes in this release that can be used to significantly reduce disk IO with: > 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks > 2) When mail storage and INDEX storage are separated Thanks for these changes! Big win for my setup. My servers are not overly stressed, but how much performance

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

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:

Timo Sirainen wrote: Thanks for the reply -- I think I can now write a new config to test these tasty features out. >>> + mail_location can now include NO-NOSELECT parameter. This >>> automatically deletes any \NoSelect mailboxes that have no children. >>> These mailboxes are sometimes confusing to users. >> >> Sorry for my IMAP ignorance, but how can

Hello Timo, I am quite eager to test it, but I don't know if these changes can be applicable for my configuration (it is shared storage one, any mdbox on NFS can be accessed by multiple servers, I made it so it's mostly accessed by one, but at certain conditions multiple servers still access mailbox simultaneously). So if possible I want to ask few dumb questions: - I assume

On 16 Aug 2017, at 8.37, Alexey Asemov (Alex/AT) <lists at alex-at.ru> wrote: > > Hello Timo, > > I am quite eager to test it, but I don't know if these changes can be applicable for my configuration (it is shared storage one, any mdbox on NFS can be accessed by multiple servers, I made it so it's mostly accessed by one, but at certain conditions multiple servers still

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

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz.sig A couple of changes since rc1: + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - director: v2.2.31 caused rapid reconnection loops to directors that were down. Also this was already in rc1's list of changes, but wasn't actually in

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc2.tar.gz.sig A couple of changes since rc1: + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - director: v2.2.31 caused rapid reconnection loops to directors that were down. Also this was already in rc1's list of changes, but wasn't actually in

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:

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