The Zimbra Collaboration Suite logs its activities and errors to a combination of system logs through the syslog daemon as well as Zimbra specific logs on the local file system.
The logs described below are the primary logs that are used for analysis and troubleshooting..
Upgrading is really quite easy, as there are not many backwards compatibility breaks.
If you are not sure which version a function or feature is in, you can check the PHP documentation on the website.
(Note: prior to ZCS 4.5, this log was called The Zimbra syslog details the activities of the Zimbra MTA (Postfix, amavisd, antispam, antivirus), Logger, Authentication (cyrus-sasl), and Directory (Open LDAP). This allows syslogd to capture data from several ZCS components including Postfix, Amavis, Clam AV, mailboxd, zmmtaconfig, and logger.
This website will also not tell you which tools to use, but instead offer suggestions for multiple options, when possible explaining the differences in approach and use-case.
Geo Event Server will incorporate the event data into the content body of a REST request and send the request to the external server as an HTTP/POST.
This capability has been available in the last several releases., however, might prefer to receive requests with event data organized as query parameters rather than in a request's content body.
Both parties of a replication session must authenticate to the other using SSL certificates. The following sections describe how to configure replication in the directory server.
For information about the mechanics of the replication process see Chapter 5, "Understanding the Oracle Unified Directory Replication Model".