Compared to MS Exchange and Groupwise Zarafa was the solution with the lowest TCO.
Use debconf to configure Exim4 for which domains Exim should consider itself as the final destination. You can do this with the following command:
dpkg-reconfigure plow exim4
Create a file called 700_exim4-config_zarafa in the directory /etc/exim4/conf.d/router. Add the following text in the file:
zarafa:
debug_print = "R: zarafa for $local_part@$domain"
driver = accept
domains = +local_domains
check_local_user
transport = zarafa_pipe
require_files = +/usr/bin/zarafa-dagent
no_verify
no_expn
Create a file called 30_exim4-config_zarafa_pipe in the directory /etc/exim4/conf.d/transport. Add the following lines to the file:
zarafa_pipe:
debug_print = "T: zarafa_pipe for $local_part@$domain"
driver = pipe
path = "/bin:/usr/bin:/usr/local/bin"
command = "/usr/bin/zarafa-dagent $local_part"
return_path_add
delivery_date_add
envelope_to_add
Finally you need to add the following line to the file /etc/exim4/update-exim4.conf:
dc_localdelivery=zarafa_pipe
Now start the update-exim4.conf script and reload Exim4 with the following commands:
update-exim4.conf
etc/init.d/exim4 restart
The Zarafa Summercamp 2010 came to an end on Friday the 18th of June – a 2 day conference which again drew a lot of interest, cementing its position at the top of European open source vendor events, through even higher attendance numbers than in 2009 and intensified contributions of community members and partners.
At the second day of its Summercamp, the Dutch mobile messaging and collaboration specialist Zarafa launches an integration framework that will give the open source community and commercial integrations with Zarafa's Collaboration Platform a next big boost.
![]() |