Jakob Bohm writes:
Alternatively (third fallback), a clear statement regarding the ability of Courier-IMAP to work with folders that are symlinked into multiple locations (this requires extensive scripting to create and remove symlinks as folders come and go, but might be doable if it doesn't upset the internal logic in Courier).
Should be fine, except for one aspect. This isn't much different than multiple IMAP servers using the same folder, which is what happens when you use real shared folders.
Except that each client will have the ability to delete the folder, which will happily delete every message in the folder. Real shared folders use ACLs to prevent that. But you have some exposure here. The IMAP server needs write access to the maildir, in order to move new mail from new to cur, as well as update some metadata files in the mail folder's root. Which means that the IMAP server will have write access to remove any message in the shared folder, and remove the entire folder. Which won't be good.
I would recommend that you hack the code and modify it to reject a DELETE of a shared folder. Come to think of it, I like this idea myself: refuse to DELETE or RENAME some folder if it's a symbolic link.
P.S. I am aware that the Courier suite includes a modified Squirrelmail
It's not a modified Squirrelmail. It's original code, a webmail client written from scratch.
pgpjSB9409R46.pgp
Description: PGP signature
------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
