The main view that the user sees will look like this. The folder list in the left hand side has been enriched with information about the IMAP shared folders, namely their post address and description, taken straight from LDAP. A handy icon for posting to the folder is there, too.

[shared_folder_view.png] An IMAP shared folder looks like the one in this screenshot. The folder's description is displayed on the top of the page; it has previously been fetched from the LDAP server.
[message_view.png] A typical message view will show the usual Squirrelmail utilities, as well as a Reply to Folder functionality, akin to Reply to List only. Reading this screen's text will reveal more details. :)
[compose.png] The compose screen is pretty much standard Squirrelmail stuff. However, the chosen "identity" can be switched on the fly. The usual utilities (spellchecker, variable sent folder et al) are here.
[folders_page.png] The standard Squirrelmail folders page; here subscriptions to shared folders can be made.
[subscription.png] As an alternative, there is a special subscription page that shows each folder's descriptions, straight from LDAP and adapted for the current locale.
[options.png] Overview of the available options pages. Most of these options that constitute the user's profile are stored on the LDAP server. And the Change Password functionality applies, of course, to the LDAP too.
[options_personal.png] The personal options page allows for a different reply-to address, but not for a different name or From: email. No more sending messages as whoever the users feel like being on a named day, since these are taken from LDAP, are not allowed to change from the interface and are filtered by Sendmail using FromFilter.
[advanced_identities.png] Squirrelmail respects the mailAlternateAddress multivalue field in LDAP; the advanced identities page allow the user to choose between the available "identities" that she can show in her outgoing messages.
[options_highlight.png] The standard message highlighting options screen.
[directory_service.png] The directory service serves as a global addressbook; the utility respects international names encoded in UTF-8 on the LDAP.
[filters_table.png] The SIEVE server-side mail filtering applies to the user's incoming emails upon delivery. This screen shows a good overview of things that are possible with SIEVE. And it's all stored on the server, meaning that the user will get the same folder view in the end, whether she's viewing her mailboxes from Outlook or Squirrelmail.
[filters_headers.png] Here, while choosing the "If" part of a filter rule, the user can choose from a variety of options for fine-grained SIEVE scripts -- all with a nice graphic interface.
[filters_actions.png] This screen shows the massive number of actions that are possible with the SIEVE filtering scheme and its extensions. Apart from the usual "redirect" and "move into folder", there is also functionality for vacation, notification methods (assuming they are supported at the Cyrus end) and rejects with configurable messages to be sent.
[mini.png] Jason Munro's "mini" plugin for Squirrelmail, in action.

Thubmnails generated by HTMLThumbnail 1.1.4