Jakob Bohm writes:
Hi,The shared folder mechanism described in the Courier documentation seems to be exclusively about "newsgroup-style" shared folders where each individual user getshis own mail status flags (such as seen/unseen).
There are two different kinds of shared folder mechanisms that are described in the documentation. Only one of the two has the semantics that you're referring to here, filesystem permission-based shared folders.
"pool-style"shared folders, where the status of e-mails is shared amongst all users, so only one user will typically need to handle an e-mail (one example would be the folder receiving mails sent to a role-account such as [email protected], where morethan one person is watching this inbox and replying to requests).
This would be the semantics of virtual shared folders.Note, that on a given platform either filesystem or permission-based shared folders can be implemented, or virtual shared folders. That depends on how the mailbox uids and gids are set up. If each mailbox uses a unique uid, you can only set up filesystem permission-based shared folders. If all mailboxes share the same uid, you can only use virtual shared folders.
If your mailboxes have unique IDs, virtual shared folders will not work. If your mailboxes have the same ID, filesystem permission-based shared folders will not work. Whether you need to use one or the other depends on how you've configured your mailboxes.
See http://www.courier-mta.org/imap/README.sharedfolders.html
pgp12FwDSb0Vs.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
