[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sqwebmail
Subject:    [sqwebmail] SqWebMail 20040216
From:       Sam Varshavchik <mrsam () courier-mta ! com>
Date:       2004-02-17 2:55:15
Message-ID: cone.1076986515.343808.28185.501 () ny ! email-scan ! com
[Download RAW message or body]


Download: http://www.courier-mta.org/download.php#sqwebmail

This build adds a partial implementation of virtual shared folders.

It's based on the same virtual shared folder code base as Courier-IMAP.
When complete, both implementations will interoperate, but not right now.

This is a new implementation of shared folders that can be used with virtual
accounts.  The existing shared folder implementation, based on filesystem
permissions (and therefore cannot be used with virtual accounts), is still
available.

This virtual shared folder implementation is based on IMAP access control
lists.  The file "maildir/README.sharedfolders.(html|txt)" has been updated
accordingly.  This README focuses on setting up shared folders, and does not
really explain how access control lists work.  Here's some additional
reading material for that:

• The man page maildir/maildiracl.1, or maildir/maildiracl.html

• http://www.ietf.org/internet-drafts/draft-ietf-imapext-acl-09.txt

Although the current development Courier-IMAP build already has complete ACL
support, the webmail initially implements only the "administer" and "lookup
(visible)" access controls.  A small icon, which should look like a key, is
placed next to each folder.  This icon brings up a new page where access
control lists may be entered.  At this point, you really need to review the
documentation referenced above (if necessary) in order to know what to enter
on that page.

Although that page allows all access controls to be set, webmail knows about
"administer" (being able to view the ACLs in the first place) and "lookup
(visible)".  The remaining access controls are to be done.

Other things that will not work in webmail, yet:

• Copying messages to shared folders

• Renaming shared folders (deleting and creating shared folders should
work)

About the only thing that will work now is that publicly-shared folders with
lookup rights will become visible, and may be opened and read.

This build is made available mostly to find anything that might be broken
(aside from the unimplemented stuff); especially the existing,
filesystem-based, shared folders which should not be affected at all.



[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]