similar to: BUG: cannot move messages to root mailfolder in namespace "There can be only one namespace with inbox=yes"

> >> >> I can only move messages to a root namespace folder when specifying >> inbox=yes. That is strange because it is not even the inbox. I don't >> even get why it is not by default possible, maybe bug there? >> > >This makes no sense. inbox=yes namespace means the namespace which has >'INBOX' folder as per RFC. With this

Hi, this setting might work. The default namespace "inbox" is managing INBOX and defines Special-Use folders on the same hierarchic level as INBOX. There is an extra namespace "4archives" which defines Archive as a mailbox on the same level as INBOX but stored on a different location. Set mailbox attribute auto to your liking. namespace inbox { type = private disabled = no hid

> >> >> I get this error message from apple mail when I right click and choose >> archive >> "The IMAP command "UID COPY" (to Archive) failed for the mailbox "INBOX" >> with server error: Mailbox isn't selectable" >> > >Did you notice that you have a mailbox called 'Archive' and namespace called

> On 31 December 2018 at 15:47 Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > > > > > >> > >> I can only move messages to a root namespace folder when specifying > >> inbox=yes. That is strange because it is not even the inbox. I don't > > >> even get why it is not by default possible, maybe bug there? > >>

Hi Martin, Thanks for the reply. I got the error below, but when I changed the prefix in 4archives to Archive/ I am getting indeed something that is looking ok, I still have to test with a few clients. Why did you call the namespace 4archives? Because it would load before inbox? Or does this not matter at all. Error: namespace configuration error: Duplicate namespace prefix: ""

> On 30 December 2018 at 17:09 Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > > > > I can only move messages to a root namespace folder when specifying > inbox=yes. That is strange because it is not even the inbox. I don't > even get why it is not by default possible, maybe bug there? > This makes no sense. inbox=yes namespace means the namespace which

Where is a manual describing how to do this? Archive tree on different storage? ??? Archive/Archives/Archived Messages/Archived mail <- need to store messages in root folder also ??? ??? 2017 ??? ??? ??? projects ??? ??? ??? ??? project ??? ??? ??? ??? project1 ??? ??? ??? ??? project2 ??? ??? ??? ??? project3 ??? ??? ??? ??? project4 ??? ??? ??? ??? project5 ??? ??? ??? Sent Messages ???

Interesting. While I don't use mbox (dbox or maildir) I wouldn't think that would matter. Your namespace layout looks nearly the same as my own. But to verify what's going on - post the output of "doveconf namespace". Possibly just reviewing that output may tell you enough - otherwise share it (fully) here. -- Daniel On 1/23/2020 12:46 PM, Gregory Sloop wrote: >

> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote: > > > I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 > > > Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:

Dne 07.09.2020 v 12:43 Sami Ketola napsal(a): >> On 7. Sep 2020, at 12.38, Miloslav H?la <miloslav.hula at gmail.com> wrote: >> >> Hello, >> >> I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). May I ask you

Hello, I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). May I ask you for the comments as from people around the Dovecot? We are using btrfs RAID-10 (/data, 4.7TB) on a physical Supermicro server with Intel(R) Xeon(R) CPU E5-2620 v4 @

http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already

http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already

Hi, I am running two dovecot servers active/active. Everything runs pretty great, except for the replication of subscriptions in a shared namespace. When I unsubscribe from a folder the subscription instantly re-appears. The timestamp on the subscriptions file is updated, but the entry is still in there. If the other node is shut down, everything works as expected, which leads me to believe that

Hi there! I recognized that dovecot ignores users sieve-script. The global and the post-sieve-scripts are working, but users sievescript is ignored. You can see the sieve trace-files last lines ? 65:?? finishing match with result: not matched ? 65: jump if result is true ? 65:?? not jumping ? 65: jumping to line 67 ? 67: jumping to line 77 ????? ## Finished executing script 'global' ? ?

Hi, I had an old dovecot server with a working backup script. Basic concept was: - to dsync to a temp folder - using tar to preserve datetime - piping this 7z to benefit from my 16 core cpu - piping this through openssl to encrypt Over time the size of all my mail grew from 3GB to about 70GB. I used to keep the last 14 backups, but this uses a lot of space. I now want to dsync my

In my email archiving setup, no user will have an inbox (regular mail is taken care of by another system). Is it not possible to configure a dovecot setup without an inbox? /Per Jessen, Z?rich

Hi all, I am currently facing an issue with Dovevot version 2.2.29.1 where subfolders in a public namespace are only visible to the 2nd folder level: namespace Public -> folder "1st" -> folder -> "2nd" -> folder "3rd" .... When one user creates a subfolder below the 2nd level other users do not see that folder and are unable to subscribe to this

Hi there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log J?n 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>: Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed:

I'm trying to setup a new server on centos 6, from old dovecot 1.x I installed 'dovecot --version 2.1.1' from dovecot rpm I converted conf file as per migration specs, also, copied sql conf across when I try to retrieve email, log has *1: dovecot.conf -m *2 and sql conf *3 follows *1------------------------------- dovecot: master: Dovecot v2.1.1 starting up (core dumps disabled)