==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
http://bugs.contribs.org/show_bug.cgi?id=7177
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
--- Comment #1 from Paul Floor <[email protected]> ---
HF,
I have taken smeserver-zarafa and built "smeserver-zarafa-unix" for Zarafa 7.X
on SME8. This implementation uses the unix plugin and automatically
authenticates to all unix users. It also uses the exclude logic that I asked
the zarafa developers add to exclude all the duplicate users that are also
groups. The exclusions are automatically taken care of by the template for the
unix plugin's config file, unix.cfg.
I stripped out the user panel that was in the original version because it was
not written per SME standards and would directly update config files by not
using templates. It also is no longer needed as all users are simply
created/deleted whenever you add or delete a user in SME. It also keeps the
passwords in sync.
You can access zarafa by mydomain/zarafa and if webmail is off, the template
also redirects mydomain/webmail to the zarafa webmail client. If webmail is
enabled in the server-manager, /webmail goes to horde. This could easily be
tweaked and used as a direct replacement for horde by simply changing the
default ports and a few minor changes to some templates.
All the necessary service and template expansions are there and there is even a
couple events to start, stop and update the services. There are templates DB
settings to configure the way mail is directed either to maildir or zarafa for
each user. By default it is set to global.
The install script calls an install/update event that will create the database
and choose a 72 char random password for enhanced security. The event also
sets the proper file ownerships for zarafa and z-push (if installed).
There are some other DB entries that allow global use of zarafa or on a "per
user" basis. If Horde is removed, these settings may need be removed.
It is very stable and worked for me up to a couple months ago and is for the
most recent version as long as there is an available php53-mapi rpm built. As
you may (or may not) know, zarafa does not work out of the box with Centos5
because Centos5 uses php 5.3 and someone has been building a php53-mapi rpm but
they are usually a few versions behind.
If you are interested, you may download them from here...
http://smeserverpro.com/smeserver-zarafa-unix-1.0.1-3.noarch.rpm
http://smeserverpro.com/smeserver-zarafa-unix-1.0.1-3.src.rpm
I will leave them there for 30 days for you.
thanks,
Paul
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
