Glad its finally hit the ground
Good to see the facility to appoint a user as "Zarafa admin" to manage the public folders. Perhaps the default quote should be higher than 100MB? that doesn't go far...and would be better to drill it down from unlimited if required?
From my experience with Zarafa the system-mysql backend is fine until you need to dump or restore it for backup purposes. It causes headaches, and the Zarafa provided scripts for database manipulation don't work (case in point is their script to move attachments from Mysql to the filesystem). Nothing more than a general inconvenience such as having to find your system-mysql password, and the Zarafa database etc...
Having Zarafa Webaccess running off the standard web server simplifies things somewhat. I only moved it in 5.2 so that it was not dependant on the PHP version as there were many and the php-mapi extension had to be rebuilt. Because no one likes to remember port numbers in URLs I also used a ProxyPass config to pass data to the webconfig in 5.2...IMHO this added extra complexity and made it hard to implement https connections for webmail, and also complicated z-push. If we can i'd like to see webaccess https only using the normal web server...
I've never really investigated it, but Zarafa offers a Zarafa-contacts functionality such that users can store contact information in LDAP...is that feasible?
Good to see the 'webapp' in the repo too, this is the ultimate replacement of webaccess and is pretty reliable from my testing in 5.2
Will Zarafa support a multi-tenancy setup? or are you still going for the single mail domain target for SOHO use
Its also been requested in the past to be able to configure 'zarafaSendAsPrivilege' so that nominated users can send on behalf of someone else. Such that firstname.lastname@example.org
can actually appear as email@example.com
when sending mail. I couldn't spot a better way of achieving except without some clever maps in postfix to change outgoing mail. Is it possible to select the outgoing mail based on the users list of predefined aliases?
Last one! for some reason the default /etc/zarafa/server.cfg disables POP3 and IMAP (see disabled_features = imap pop3), not really sure why - it would appear you can then enable POP/IMAP access on a per user basis, but thats not a setup i'd see frequently? It would be better to enable globally...