similar to: \Noselect isn't set on namespace prefix mailbox that can't be selected

Hi, With mailbox_list_index enabled (which is the default), Dovecot won't return \Noselect when LISTing a mailbox that was deleted but still has subordinate mailboxes. Before creating such a mailbox in the first place, it does return \Noselect. 1 LIST "" Test 1 OK List completed (0.002 + 0.000 + 0.001 secs). 2 CREATE Test/Test 2 OK Create completed (0.014 + 0.000 + 0.014 secs). 3

I enabled NO-NOSELECT in mail_location as it seemed to be an optimization without negative consequences. The wiki states NO-NOSELECT : Automatically delete any \NoSelect mailboxes that have no children. These mailboxes are sometimes confusing to users. Also if a \NoSelect mailbox is attempted to be created with "CREATE box/", it's created as selectable mailbox instead. The

In virtual namespace I can have: namespace myvirt { location = blah prefix=Virtual/ separator=/ mailbox "My folder" { auto = subscribe } } And i see email clients successful display subscribed "My folder" but the top-level prefix "Virtual/" is not subscribed. I see the Virtual/ prefix available as a noselect folder in the list of unsubscribed

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

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) "."

FYI in subscription file for namespace I see empty line when the top level prefix is subscribed. Works perfectly just need to make it automatic On 2019-05-08 20:50, MRob via dovecot wrote: > In virtual namespace I can have: > > namespace myvirt { > location = blah > prefix=Virtual/ > separator=/ > > mailbox "My folder" { > auto = subscribe

Hello, I am trying to use two namespaces to create an "archival" directory that is stored as mboxes (the rest of my tree is all stored as maildirs). However, when I add the second namespace, suddenly Dovecot starts emitting, in response to the LIST command, a second version of the INBOX that is marked as \NoSelect. Here are my namespac definitions... am I doing this wrong?

I am utilizing a public namespace via http://wiki2.dovecot.org/SharedMailboxes/Public and using sdbox storage format. How can I get rid of the \Noselect flag that is set by default for this folder? IMAP output: b LIST "" "*" * LIST (\HasNoChildren \Sent) "/" Sent * LIST (\HasNoChildren \Trash) "/" Trash * LIST (\Noselect \HasNoChildren) "/"

> On 26 September 2018 at 18:42 Daniel Miller <dmiller at amfes.com> wrote: > > > 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

Aki, you were right. It was at /usr/lib/dovecot Here is the output: root at mail:~# /usr/lib/dovecot/imap -u m.markov * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT

Hi, I noticed a difference between courier and dovecot, and I'm not sure which of them is wrong wrt. RFC3501 - if any. I have a Maildir which has been accessed by an Apple Mail client, so it got folders like: INBOX INBOX.Trash INBOX.INBOX.folder INBOX.INBOX.folder.a INBOX.INBOX.folder.b The INBOX.INBOX folder does not exist on disk and is not subscribed. Courier responds to: . list

Hi Timo, We have encountered an issue today with a number of migrations. Some customers have mailboxes on the source IMAP server that look like this: 3 LIST "" * * LIST () "." "INBOX" * LIST () "." "INBOX.Statements" * LIST () "." "INBOX.Draft" * LIST () "." "INBOX.Drafts" * LIST () "."

Hi, I'd like to share the whole INBOX of one user with another. That should go through: doveadm acl add -u user1 at example.cz SharedDirectory user=user2 at example.cz lookup read insert It's works fine, when I connect through imap I see: . list "" "*"* LIST (\Noselect \HasChildren) "/" shared* LIST (\Noselect \HasChildren) "/"

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

I don?t seem to have that install on my Debian machine. But I have done this: 1 LIST "" % * LIST (\HasNoChildren) "/" confirmed-spam * LIST (\HasChildren) "/" Archive * LIST (\HasNoChildren \Sent) "/" Sent * LIST (\HasChildren \Trash) "/" Trash * LIST (\HasNoChildren) "/" Spam * LIST (\HasChildren) "/" Archives * LIST

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

Timo, examine these two simplified sets if you will. This, is a properly working $inbox folder: d /home/david/.maildir /home/david/.maildir/dovecot.* d /home/david/.maildir/cur d /home/david/.maildir/new d /home/david/.maildir/tmp /home/david/.maildir/subscriptions This one is not, $inbox becomes \Noselect: d /home/david/.maildir /home/david/.any-file /home/david/.maildir/dovecot.* d

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

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

I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST"