83
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.
{{Note box| This contrib uses the unix plugin and automatically and properly enables all valid users as Zarafa users and all valid groups as Zarafa groups. Everything is initially done automatically for you by the post-install event so you do not need to do anything further. In addition, when you add or delete a user or group from the server manager, the user or group is automatically added or deleted in Zarafa. Also, any password change will automatically change the zarafa login password to match.
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}
By default, Zarafa is enabled for all users except admin. You can change this to 'per user' via db entries.}}
Now install smeserver-zarafa-unix by performing the following:
Now install smeserver-zarafa-unix by performing the following:
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)
yum install smeserver-zarafa-unix --enablerepo=smedev (NOTE: This will not work until the mirrors are updated.)
NOTE: On the GPL version you must disable zarafa-licensed...
NOTE: On the GPL version you must disable zarafa-licensed...
config setprop zarafa-licensed status disabled
config setprop zarafa-licensed status disabled
After rpm install execute the following:
After rpm install execute the following:
signal-event zarafa-post-install
signal-event zarafa-post-install
signal-event post-upgrade; signal-event reboot
signal-event post-upgrade; signal-event reboot
=====To disable global Zarafa for all users=====
To disable global Zarafa for all users...
config setprop zarafa-server GlobalForward disabled
config setprop zarafa-server GlobalForward disabled
signal-event user-modify
signal-event user-modify
To enable an individual user if Global is disabled...
=====To enable an individual user if Global is disabled=====
db accounts setprop $USERNAME zarafa enabled
db accounts setprop $USERNAME zarafa enabled
signal-event user-modify $USERNAME
signal-event user-modify $USERNAME
To enable the admin account...
=====To enable the admin account=====
db accounts setprop admin zarafa enabled
db accounts setprop admin zarafa enabled
signal-event user-modify-admin
signal-event user-modify-admin
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz
====Mobile synchronisation====
=====Known working hardware=====
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.
Tested and working with Android 4.1.1 on a Samsung Galaxy 3S over a SSL connection / mail-push is working.
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.
====Additional Mobile Synchronization Information====
====Mobile synchronisation====
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.
z-push now has RPM's built for RHEL6 making the install simple...
For i386 go here http://download1.rpmfusion.org/free/el/updates/6/i386/repoview/letter_z.group.html
For X86_64 go here http://download1.rpmfusion.org/free/el/updates/6/x86_64/repoview/letter_z.group.html
You will need 2 packages, <b>z-push</b> and <b>z-push-zarafa</b>. Download the latest packages, as of this writing, 2.0.7-1 works without any issue.
yum localinstall z-push*
*save resulting .cer certificates on local machine
=====Know working hardware=====
=====Know working hardware=====
Tested and working with Nokia 6120 Classic. Push mail not tested.
Tested and working with Nokia 6120 Classic. Push mail not tested.
=====Additional Mobile Synchronization Information=====
'''SSL Synchronization with Windows Mobile devices'''
Synchronization over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.
This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.
Here are the steps to add your server as a trusted platform on your WM6 mobile :
1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.
openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER
2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer
3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :
*in microsoft windows open a certificate by double clicking on it
*in "Detail" Tab pane choose "Copy to file"
*Choose Binary coded DER X.509 (.cer) format
*save resulting .cer certificates on local machine
4. transfer .cer certificates on your mobile using windows explorer
5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.
6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.
====Command line admin====
====Command line admin====
