In my setup, I have approximately 18 users using thunderbird with SOGo connector and lightening to sync calendar information with a single SOGo server.

This causes SOGo to flood both it's log and the nginx log with messages related to dav OPTIONS, PROPFIND, and REPORT functions. These logs can easily exceed 4GB each in a single day.

After assessing these logs, I determined that they are purely informational and the decision was made to discard them because they endanger the health of the server.

In nginx, discarding access logs related to SOGo dav involved adding a single directive to nginx's conf file. With SOGo, I found that this is not possible.

Regarding SOGo, there are two problems:

1. SOGo does not write to syslog. It writes directly to it's own log. Therefore a user cannot leverage their syslog daemon's functions to filter specific messages. ;(

2. SOGo only has an option in the configuration to increase the verbosity of logging, not to filter specific logs or disable logging entirely. ;(

Accepting this, my work around entailed creatign a symbolic link from /var/log/sogo/sogo.log to /dev/null. I don't particularly like doing this. However, I don't see how I have any choice since SOGo has caused outages 3 times in the past.

As a recommendation, I would like SOGo's developers to consider the following with regard to ease of use and scalability:

1. Changing SOGo to use a standard logging mechanism that system administrators are capable of reasonably managing such as syslog.

2. Add an option to disable logging altogether from the config file.

3. Add an option to disable output for specific categories or logs: ie. "access", "dav", "web", "calendar", etc, etc

4. Add an option to disable logs that match a regex