When a Maildir that contains one or more read-only shared folders is never read directly, i.e. no one ever logs in to the maildir via IMAP, subscribed users cannot read newly arriving mails, because they stay forever in the "new" directory of the shared folder.

Accoring to README.sharedfolders, this happens: <quote> * Read the contents of shared-folder/name/shared/.foldername/new. If you find anything in there, rename it to .../cur, ignoring any errors from the rename. The sharable maildir owner can arrange for mail to be delivered directly to this folder, and the first one to open it will put the message into cur. </quote>

Unfortunately, the "ignoring any errors from the rename" part also means to ignore the message, i.e. only messages from the "cur" folder have symlinks created to them from the subriber's folder, but not the ones in "new". I can workaround this easily with a cron script that peridically moved any files from new to cur, but that'll become a maintenance nightmare when I'll add more shared folders which is planned :-)

Another thing that bugs be is that it seems impossible to share the main folder of a sharable Maildir. Rationale: for users, the tree

INBOX -- INBOX.foo -- INBOX.bar shared -- shared.dept1 -- shared.dept1.announce -- shared.dept2 -- shared.dept2.announce

Is rather inconvenient, would be nice to lose the intermediate level from the above hierarch and instead have the mails of dept[12].announce inside their maildir's main folder, since the maildir contains only one folder anyway... Is this possible?

TIA, -Malte