Another consideration that must be made is if unread messages should be stubbed and/or deleted. One could argue that an unread message shouldn’t be stubbed because the user is likely to read it soon and needs fast access. On the other hand one could argue that since the user still hasn’t read the message during the time it’s available on the primary node, chances are the user isn’t going to read it soon.

So if the policy would be to stub unread messages but not delete them, the following settings should be set in /etc/zarafa/archiver.cfg

stub_unread     = yes
delete_unread   = no