Difference between revisions of "Talk:Zarafa"

From SME Server
Jump to navigationJump to search
(remove config performed in rpm, and instructions on main page)
m
Line 1: Line 1:
−
== Rough Guide to get Zarafa running. Lots more to do... ==
 
−
http://forums.contribs.org/index.php?topic=42118.0
 
−
 
−
===Misc.===
 
−
List users:
 
−
/usr/bin/zarafa-admin -l
 
−
 
−
Update a user to admin status:
 
−
/usr/bin/zarafa-admin -u <username> -a 1
 
−
 
  
 
===Issues===
 
===Issues===
  
 +
====.qmail====
 +
* spam could be sorted to ~/Maildir/junkmail
  
−
====.qmail====
 
 
* The smeserver-mailsorting contrib sorts to Maildir folders,  
 
* The smeserver-mailsorting contrib sorts to Maildir folders,  
 
zarafa won't see this mail. Disable procmail/maildrop and re-create internal zarafa rules
 
zarafa won't see this mail. Disable procmail/maildrop and re-create internal zarafa rules
Line 57: Line 48:
 
We don't want machine names, ibays, system, the group of a user, maybe others.  
 
We don't want machine names, ibays, system, the group of a user, maybe others.  
 
I don't see how to hide them, changing shell to /bin/false may break things
 
I don't see how to hide them, changing shell to /bin/false may break things
−
 
−
====Folder Naming====
 
−
SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.
 
−
 
−
drafts > Drafts
 
−
junkmail > Junk E-mail
 
−
sent-mail > Sent Items
 
−
trash > Deleted Items
 
−
 
−
====Migrating users and data to Zarafa====
 
−
Zarafa migration whitepaper describes various ways of migrating your users and your data to a Zarafa server.
 
−
 
−
http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf
 
−
 
−
=====IMAP migration from SME/IMAP to Zarafa/IMAP=====
 
−
 
−
Configure zarafa-gateway for migration enabling IMAP on port 144 only as shown above
 
−
 
−
Get imapsync and required perl module
 
−
 
−
wget http://dag.wieers.com/rpm/packages/perl-Mail-IMAPClient/perl-Mail-IMAPClient-2.2.9-1.2.el4.rf.noarch.rpm
 
−
yum localinstall perl-Mail-IMAPClient-2.2.9-1.2.el4.rf.noarch.rpm
 
−
 
−
wget http://www.linux-france.org/prj/imapsync/dist/imapsync-1.264.tgz
 
−
tar -zxvf imapsync-1.264.tgz
 
−
cd ./imapsync-1.264
 
−
make install
 
−
 
−
Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2)
 
−
 
−
imapsync --noauthmd5 --host1 localhost --port1 143 --user1 <username> --password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 <username> --password2 <password>
 
−
 
−
Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:
 
−
 
−
imapsync --noauthmd5 --host1 localhost --port1 143 --user1 bob --password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 bob --password2 bob123
 
−
 
−
After syncing is complete, stop zarafa-gateway service and/or edit /etc/zarafa/gateway.cfg to meet your needs.
 
  
 
===SME Actions===
 
===SME Actions===

Revision as of 09:38, 5 October 2008

Issues

.qmail

  • spam could be sorted to ~/Maildir/junkmail
  • The smeserver-mailsorting contrib sorts to Maildir folders,

zarafa won't see this mail. Disable procmail/maildrop and re-create internal zarafa rules

sv sigusr1 httpd-e-smith

Eg. modifying an ibay, causes a problem with webaccess 

tail /var/log/messages
<snip>
Sep 28 16:30:27 kiwi httpd: PHP Warning:  Function registration failed - duplicate name - mapi_zarafa_getuser in Unknown on line 0
Sep 28 16:30:27 kiwi httpd: PHP Warning:  Function registration failed - duplicate name - mapi_zarafa_getgroup in Unknown on line 0
Sep 28 16:30:27 kiwi httpd: PHP Warning:  mapi:  Unable to register functions, unable to load in Unknown on line 0

most of these events will cause webaccess to break 

# ls -la `slocate services2adjust | grep httpd-e-smith`
/etc/e-smith/events/console-save/services2adjust/httpd-e-smith -> restart
/etc/e-smith/events/domain-create/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/domain-delete/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/domain-modify/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/email-update/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/host-create/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/host-delete/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/host-modify/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/ibay-create/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/ibay-delete/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/ibay-modify-servers/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/ibay-modify/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/ldap-update/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/logrotate/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/network-create/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/network-delete/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/remoteaccess-update/services2adjust/httpd-e-smith -> sigusr1
/etc/e-smith/events/timezone-update/services2adjust/httpd-e-smith -> restart

workaround is to 

sv restart httpd-e-smith

fix is to work out why php is giving an error

Address book

The Zarafa global address book finds users and groups from /etc/passwd etc/group

We don't want machine names, ibays, system, the group of a user, maybe others. I don't see how to hide them, changing shell to /bin/false may break things

SME Actions

Actions to be linked into events

user-delete

To delete a user from the server, use the following command: 

 /usr/bin/zarafa-admin -d <user name>

The user will be deleted from the database. The store of the user will be placed in the public store, in a 'Deleted Stores' folder. This folder is only available to administrative users of Zarafa.

Retrieved from "https://wiki.koozali.org/index.php?title=Talk:Zarafa&oldid=10769"