Koozali.org: home of the SME Server

Contribs.org Forums => General Discussion => Topic started by: gbentley on June 18, 2011, 12:25:41 PM

Title: How to config syslog to exclude certain messages frorm /var/log/@maillog
Post by: gbentley on June 18, 2011, 12:25:41 PM
Following a change of 3rd party services recently I have found fetchmail filling up the log above with ;

'Server CommonName mismatch' type messages!

Googling about on this I have deduced its harmless noise [mail does in fact work fine] but I'd like to exclude
these mesages from the logs.

I dont know much about syslog so I was wondering how would I go about doing this on SME?

Thanks in advance for any advice :)

Edit: I have now added

Code: [Select]
--sslproto '' to my custom fetchmail template and this has stopped the messages however I still would be interested to learn about syslog on SME :)
Title: Re: How to config syslog to exclude certain messages frorm /var/log/@maillog
Post by: CharlieBrady on June 19, 2011, 05:50:34 AM
Googling about on this I have deduced its harmless noise [mail does in fact work fine] but I'd like to exclude
these mesages from the logs.

AFAIK, you can't configure syslog to ignore messages based on content of the messages. Message logging is controlled by 'facility' and 'priority' and nothing else. Unless the messages you want to exclude are a particular facility.priority, and no other messages have the same facility.priority combination, you won't be able to configure syslog to not log those messages.

Switching to syslog-ng would give you the opportunity to pattern match - but that would be a very significant customization.

Can you avoid fetchmail? You should if possible.


Title: Re: How to config syslog to exclude certain messages frorm /var/log/@maillog
Post by: CharlieBrady on June 19, 2011, 05:52:09 AM
Following a change of 3rd party services recently I have found fetchmail filling up the log above with ;

'Server CommonName mismatch' type messages!

Those can probably be avoided if you use the hostname which is contained in the CommonName field of the SSL certificate - as long as the DNS for that name is correct.