|Martin Hochreiter||May 5, 2008 12:47 am|
|Sam Varshavchik||May 5, 2008 3:59 am|
|Martin Hochreiter||May 5, 2008 4:24 am|
|Martin Hochreiter||May 5, 2008 7:28 am|
|Sam Varshavchik||May 5, 2008 4:00 pm|
|Brian Candler||May 6, 2008 12:41 am|
|Martin Hochreiter||May 6, 2008 6:39 am|
|Brian Candler||May 6, 2008 7:54 am|
|Martin Hochreiter||May 6, 2008 8:56 am|
|Martin Hochreiter||May 6, 2008 8:58 am|
|Brian Candler||May 7, 2008 2:44 am|
|Martin Hochreiter||May 7, 2008 5:58 am|
|Peter Thomassen||Aug 8, 2008 3:58 pm|
|Sam Varshavchik||Aug 8, 2008 6:04 pm|
|Peter Thomassen||Aug 8, 2008 8:39 pm|
|Subject:||Re: [Courier-imap] Shared - Folders Problem: mails invisible|
|From:||Sam Varshavchik (mrs...@courier-mta.com)|
|Date:||Aug 8, 2008 6:04:11 pm|
Peter Thomassen writes:
maybe you are still reading this thread.
Martin Hochreiter wrote:
I setted up a test account as "host" Mailbox with the same setting as my office mailbox and tested imap on the commandline as you said.
You will find strace the output on the bottom.
There is one curious line: access("shared-folders/test/allgemein/shared/cur", W_OK) = -1 EACCES (Permission denied)
I also tried to set up a read-only shared folder. I noticed that only messages in cur/ are visible to the subscribing user, while those in new/ are not. syslog says that the rename from new/ to cur/ was denied. I suppose this is the line above, isn't it?
When there is p.ex. one message in cur/ and another one in new/, a raw IMAP session shows that there are two messages existing, where one is a recent one. Fetching the contents of the recent one fails.
http://www.courier-mta.org/imap/README.sharedfolders.html#oldsharedopen says that renaming errors from new/ to cur/ are ignored. Indeed they are, i.e. the error isn't reported to the client. To my understanding, "ignoring" means that the message is presented regardless of a renaming error.
To make messages from new/ available to all users, they must be given write access to cur/, new/ and tmp/ (I checked all combinations). This, of course, allows them to delete arbitrary messages, sapping the read-only mode.
I consider this a bug, isn't it? -- Where are bugs to be reported?
No, it's not a bug. There is no circumstance under which Courier-IMAP will place a message into the 'new' subdirectory in a shared folder. When Courier-IMAP moves a message from a private folder into a shared folder, the message gets moved directly into the cur directory.
You must be trying to deliver a message into the shared folder directly, by your mail server. This is explicitly not supported. From README.sharedfolders:
* Do NOT use this maildir as the primary mailbox, INBOX, for an account. Instead, you must create this maildir separately, perhaps as $HOME/Maildir-shared, then set it up as one of your sharable maildirs (see below), and access it in shared mode. Because you own it, you have unlimited read/write access to it. The previously mentioned options will select whether or not access permissions are given to everyone else, and they do not apply to you.
The only mechanism that may be used to place message into a filesystem permission-based shared folder is by using the IMAP client to copy messages from your personal folder to the shared folder.