crpb The problem with filtering is that you need to know what to filter for. When an update occurs in an application, the end user is unlikely to know what to look for until they find a message that needs to be filtered for. Since 14/02/26 I have had probably 40000 - 50000 of these audit entries in my http log file (sometimes as many as 30 or so a second) before this thread was started and I was able to change the log level to stop the exmdb-audit SPAM. I only have a couple of users on my Grommunio servers, so I hate to think what a 100+ user server would be like. Added to that the sheer amount of load put on the server, writing all those log messages, that does not need to be there for most of the time.
Also @crpb from your many posts in this forum you seem to be a linux/scripting guru, and you have helped/saved me (and others) much time over the last few years that I have been a Grommunio user. Unfortunately, a life in the Windows eco system has not left me well versed in the linux scripting world, so have poor scripting and syntax skills, I suspect I am not alone in this regard.
Looking back through the logs before the 14/2/26, shows that the deprecation entries were just plain text entries regarding particular config file entries, there were no '[DEPRECATED]', '[WARNING]', '[INFO]' tags on the log entries so would have been incredibly difficult to notice when wrapped in hundreds and thousands of audit messages.
Perhaps the developers could start tagging the log entries with suitable tags to enable filtering to be easier to perform for the less literate linux users. Maybe this is even something that could be added to the admin GUI (in a small summary pane of 'Warnings' etc) in the longer term (as it would likely take a fair bit of coding), so that important messages such as the 'deprecated settings' don't get overlooked because the logs are filled with 1000's of messages that are only relevant when something goes wrong, and the Admin team don't have time to check every log entry.
As @weini suggested, perhaps we need a log level between 3 and 4 that gives the useful info, deprecation and warnings without all the debug info that is only required on rare occasions.
