Difference between revisions of "Talk:Zarafa"

From SME Server
Jump to navigationJump to search
Line 64: Line 64:
 
Tested and working with WinMobile 6.1 on a HTC TyTN II over a NON SSL connection (mail-push not yet tested).
 
Tested and working with WinMobile 6.1 on a HTC TyTN II over a NON SSL connection (mail-push not yet tested).
  
Darrell, I installed Zarafa manually using custom templates/db settings and have most everything working flawlessly including the Outlook plugin, and z-push to a WM6 device and I am EXTREMELY impressed.  I have a desktop, laptop and my Samsung i760 in perfect sync.  The z-push actually "pushes" and emails, calendar, contact changes happen almost instantaneously.
+
====Additional Notes====
 +
Darrell, I have installed Zarafa manually using custom-templates/db settings and have most everything working flawlessly including the Outlook plugin, and z-push to a WM6 device and I am EXTREMELY impressed.  I have a desktop, laptop and my Samsung i760 in perfect sync.  The z-push actually "pushes" and emails, calendar, contact changes happen almost instantaneously.
  
 
I have a couple of pointers if you are still working on this project.
 
I have a couple of pointers if you are still working on this project.
Line 78: Line 79:
  
 
Some other notes:
 
Some other notes:
I totally disabled horde (no big loss there) and pop and imap.  I run zarafa on the standard ports and transitioned 15 users last night.  Some using Outlook (pop) and they didn't notice anything.  A few use webmail and I left the alias alone and those users all logged in this morning to a big surprise and they were all extremely happy.
+
I totally disabled horde (no big loss there) and pop and imap and my implementation either uses horde OR zarafa but not both.  I run zarafa on the standard ports and transitioned 15 users last night.  Some using Outlook (pop) and they didn't notice anything.  A few use webmail and I left the alias alone and those users all logged in this morning to a big surprise and they were all extremely happy.
  
 
For this to work, you need to configure zarafa to use the certs already generated in SME.  Hope this helps.
 
For this to work, you need to configure zarafa to use the certs already generated in SME.  Hope this helps.
  
 
Paul
 
Paul

Revision as of 07:31, 16 October 2008

Feedback

I uninstalled my original Zarafa setup and re-installed using the smeserver RPM Darrell created - all worked fine. I also migrated some email that I'd created in the test accounts for that purpose. This also went well. I happened to have one account in Thunderbird - the test email in the Inbox showed unread when I went into the account. However, the other account, accessed via the Zarafa web interface, showed the Inbox message as read.

Overall, the smeserver alpha RPM works well. Many thanks for it, Darrell.

Bugs

Search all bugs for smeserver-zarafa at bugs.contribs.org for history


Mobile synchronisation

Warning.png Warning:
I DON'T KNOW WHAT I'M DOING!!

PLEASE CHECK THE CODE FOR ERRORS AND SECURITY ISSUES!!

HAVE NOT FIGURED OUT HOW TO -ONLY- USE SSL YET!!



To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.

You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf


Download the latest Z-push version (see: http://z-push.sourceforge.net).

# wget http://download2.berlios.de/z-push/z-push-1.2.tar.gz

Extract the files:

# tar -zxvf z-push-1.2.tar.gz -C /var/www/html

'State'-dir needs to be writable for apache:

# cd /var/www/html/z-push/
# chmod 755 state
# chown www:www state

Make a new template fragment:

# mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/
# pico /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/86Z-PushAlias

Edit the fragment and add:

Alias /Microsoft-Server-ActiveSync /var/www/html/z-push/index.php
<Directory /var/www/html/z-push/>
   Options -Indexes
   AllowOverride None
   order allow,deny
   allow from all
   AddType application/x-httpd-php .php
   php_flag magic_quotes_gpc off
   php_flag register_globals off
   php_flag magic_quotes_runtime off
   php_flag short_open_tag on
</Directory>

Expand the template:

# expand-template /etc/httpd/conf/httpd.conf

Restart httpd (the currently for Zarafa only save way):

# sv restart httpd-e-smith

Synchronise using SSL

Incomplete.png Incomplete:
This article or section needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page



Know working hardware

Tested and working with WinMobile 6.1 on a HTC TyTN II over a NON SSL connection (mail-push not yet tested).

Additional Notes

Darrell, I have installed Zarafa manually using custom-templates/db settings and have most everything working flawlessly including the Outlook plugin, and z-push to a WM6 device and I am EXTREMELY impressed. I have a desktop, laptop and my Samsung i760 in perfect sync. The z-push actually "pushes" and emails, calendar, contact changes happen almost instantaneously.

I have a couple of pointers if you are still working on this project.

I notice you use the "db" setting for your users. I found the unix plugin a superb tool. It automatically adds all system users and keeps them in sync including password changes and user additions/deletions. It works on the fly. The only drawback is the fact SME uses weird user/group numbering so you have to include users from 5000 up and then exclude all groups by configuring uniz.cfg to a high range like 10001-10001. I also did not include admin as one of the users due to the limitations on how the unix plugin handles users/groups.

1- You need to add an alias for z-push to work.

Alias       /Microsoft-Server-ActiveSync   /var/www/html/z-push/index.php

2- I also placed a rewrite rule to force https.

RewriteRule ^/Microsoft-Server-ActiveSync(/.*|$)    https://%{HTTP_HOST}/Microsoft-Server-ActiveSync$1 [L,R]

3- You can sort junk email to zarafa and have it automatically placed in the Junk E-mail folder. This works in the .qmail-junkmail template. Note the -qj switch. This tells zarafa-dagent to place the email in the Junk E-mail folder.

| /usr/bin/zarafa-dagent -qj <username>

Some other notes: I totally disabled horde (no big loss there) and pop and imap and my implementation either uses horde OR zarafa but not both. I run zarafa on the standard ports and transitioned 15 users last night. Some using Outlook (pop) and they didn't notice anything. A few use webmail and I left the alias alone and those users all logged in this morning to a big surprise and they were all extremely happy.

For this to work, you need to configure zarafa to use the certs already generated in SME. Hope this helps.

Paul