On 18 Aug 2017, at 2.25, Joseph Tam wrote:
>
>> a CREATE noselectbox/
>> --> With this change it's the same as CREATE "noselectbox" = will become
>> selectable.
>>
>> or
>>
>> a CREATE noselectbox/childbox
>> b DELETE noselectbox/childbox
>> --> noselectbox is left
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
On 16 Aug 2017, at 23.59, Joseph Tam wrote:
>
>
> 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
On Tue, Aug 15, 2017 at 11:49:29PM +0300, Timo Sirainen wrote:
> 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
In case you are interested (and have the spare cycles), I get the
following mostly new warnings with
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
Am 15.08.2017 um 22:49 schrieb Timo Sirainen:
> https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz
my buildsystem complain on spelling errors
- in binaries
-> src/director/director-connection.c: reseting -> resetting
- in manpages
-> doc/man/doveadm-exec.1.in: wich
Hello Timo,
Many thanks for the explanation, it really clarified things.
I'll go for option (b) "Use mailbox_list_index_very_dirty_syncs=no and
put LISTINDEX to local" then and write later on if there are any issues
with it.
On 16 Aug 2017, at 8.37, Alexey Asemov (Alex/AT) 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
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
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
10 matches
Mail list logo