similar to: v2.2.32 release candidate released

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

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: 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

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: 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

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

As the subject says.? This may be a bit open-ended - but it would really help troubleshooting some obscure folder issues. In my case, I happen to have both some "real" folders and also some "virtual" folders that respond to IMAP LIST commands with the "\NoSelect" flag - and I don't know why.? Via telnet, I can manually issue SELECT, SEARCH, and FETCH for such

Hi all, can you help me to disable the "/Noselect" flag from folder so imap client can select the folder and his sub-folders to store mails inside Thanks

Hi, after upgrading from 2.0.18 to 2.1.1 I noticed that I could not use shared folders with mutt anymore. 2.1 lists the shared namespace prefix once per user sharing an folder in LIST "" "%". I also noticed, that with 2.1 the user folder (Shared/<username>) is no longer tagged as \NoSelect. Is this the intended behaviour and mutt simply cannot cope with it or is it a

Hello, is it at all possible, possibly without modifying the source code of Dovecot, to enforce that a mailbox gets the NOSELECT attribute? I have a namespace set up like this: namespace private { separator = / prefix = Local Folders/ location = maildir:/xyz/core/store/maildir/%u/ inbox = yes hidden = no list = yes subscriptions = yes } And the folder

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

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

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

On Tuesday 22 of August 2017, Timo Sirainen wrote: > 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 Oh so no way to set separate hat for each user? (based on sql query for example

On 2017-08-22 21:50:52 +0200, Arkadiusz Mi?kiewicz wrote: > > A couple of changes since rc1: > > > > + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor > > Oh so no way to set separate hat for each user? (based on sql query for > example etc) have your userdb query return an apparmor_hat column. I think dict lookups can be used as well? HTH

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

Dovecot 1.2 (8834:5284f45c249a) Should list return \HasChildren if no folders exist under it? I'm using mbox format. 2 create testfolder/ 2 OK Create completed. 3 list "testfolder/" * * LIST (\Noselect \HasChildren) "/" "testfolder/" 3 OK List completed. 4 list "testfolder/" % * LIST (\Noselect \HasChildren) "/" "testfolder/" 4

Hi, I've some virtual folders which seem a bit odd when they are listed. a LIST "virtual.spam." "*" * LIST (\Noselect \HasNoChildren) "." "virtual.spam." * LIST (\HasNoChildren) "." "virtual.spam.unchecked" * LIST (\Noselect \HasChildren) "." "virtual.spam.disagree" * LIST (\HasNoChildren) "."

RFC 3501 mentions this: The DELETE command MUST NOT remove inferior hierarchical names. For example, if a mailbox "foo" has an inferior "foo.bar" (assuming "." is the hierarchy delimiter character), removing "foo" MUST NOT remove "foo.bar". It is an error to attempt to delete a name that has inferior hierarchical

Your report is most appreciated, though it lacked quite a lot of detail that could've expedited the investigation why it happened. With the further information we can hopefully figure out why you are experiencing the problems you reported. There is no offense intended. Aki On 10.7.2019 14.01, Arnold Opio Oree via dovecot wrote: > Hello Timo, > > I have scheduled some time to carry

Hello Timo, I'm having a hard time trying to understand why Thunderbird 3.0.3 doesn't allow me to subscribe to a shared mailbox which I can subscribe to via Kmail for instance. I'm running dovecot-1.2.11/Maildir. The user 'doveimap' shares his mailbox folder/subfolder to the 'dovepop' user which should see it in the '#shared' shared namespace at the following