1. Zarafa 7.1 vs 7.0
Steve Hardy

2. New in 7.1
• zarafa-search (TIPKAZI)
• zarafa-spooler / zarafa-dagent python plugins
• ldap_uri
• zarafa-stats –session / --users / --servers / --company / --system
• Offline database change
• Multithreaded zarafa-backup
• Dagent: support for rfc1891 delivery reports
• Dagent: filtering of duplicate recipients
• No major DB changes
• Multiserver reverse proxy

3. Zarafa-search
• Used to be zarafa-indexer, but so different that we renamed it
• Major differences:
– No more support for one-to-N in cluster. So you must run one zarafa-
search per cluster node. We could add this again in the future if you
really need it
– No more ‘scanning’ of all stores every 5 minutes. Mode of operation is:
• First, scan all stores
• Enter ‘incremental mode’
• Only index changes (every 5 seconds)
– More powerful, compressed indexes in /var/lib/zarafa/index
– You must connect from zarafa-server to /var/run/zarafa-search instead
of /var/run/zarafa-indexer (this is default now in 7.1 RC1)
– Streaming of data from archive servers

4. Python plugins
• Allows zarafa-dagent and zarafa-spooler to do certain things by
adding python plugins
• No restart required when adding plugins
• Plugins currently available:
– Spooler: add disclaimer to all outgoing emails
– Dagent: convert incoming image attachments to JPG
• Other things that are possible (examples!!!):
– Add rules that are forced for all users
– Drop or forward messages for some reason
– Do OCR on incoming images and file them in the appropriate folder
• Will publish developer manual later
• Will probably mainly be used by us

5. ldap_uri
• Simple option that has been asked a lot: allows multple LDAP
servers to be specified
• Uses libldap logic to connect (first try the first one, then the next)
• Create possibilities for really bad things to happen:
– First LDAP Server is OK
– First LDAP server fails
– Zarafa-server connects to second LDAP server
– Oops, this ldap server is empty
– All stores are deleted

6. Zarafa-stats
• Better output now from zarafa-stats in table form
root@devtrunktest:~# zarafa-stats --system | head
0x3001001E 0x6740001E 0x6741001E
------------------------------------------------------------------------------------------------------------------------------------
-
server_start_date Time when the server was started Wed Jun 13 11:16:07 2012
cache_purge_date Time when the cache was cleared
config_reload_date Time when the configuration file was reloaded / logrotation (SIGHUP) Sun Jun 17 06:29:43 2012
connections Number of handled incoming connections 532796
max_socket Highest socket number used 1093
redirections Number of redirected requests 0
soap_request Number of soap requests handled by server 2128173
response_time Response time of soap requests handled in milliseconds (includes time in queue) 34721915

7. Offline database change
• After upgrade, will upgrade engine from MySQL 4.1 to MySQL 5.5
• Procedure the same as in Zarafa 7
– Upgrade starts in background
– Connects online while background upgrade is in progress
– Should take less time than the Zarafa 7.0 upgrade

8. Multithreaded zarafa-backup
• Backups STORES in parallel
• So, backing up one store cannot be done multithreaded
• Should be useful up to N threads if you have N physical (non-
mirrored) discs

9. Dagent
• Filter duplicate recipients
– Eg sending group to ‘great guys’ and ‘super smart people’ only delivers
ONE email to steve instead of two
• Support rfc1891 delivery reports
– So that means that we report OK delivery to postfix, and postfix relays
that back to the sender
– Quite unreliable since all intermediate SMTP servers must support
rfc1891

10. Recent additions past year (in both 7.0 and 7.1)
• Priority queue
– Use file:///var/run/zarafa-prio but only if you understand what you’re
doing
• LDAP paging support
• Post-MSR offline resync
– Offline sync code detects MSR of store and resyncs with new server
• MR autoresponder
– Responds to emails received in inbox. Default operation mode for OL2010
• Auto-create archive store via LDAP
– Instead of creating archive store seperately