Hi Jonathan, I'd be happy to provide guidance on this. This warning indicates you have debug log IDs enabled in your configuration which are likely impacting server performance. If you're not actively troubleshooting an issue with support at this time you can go ahead and disable these by navigating to Manage>Troubleshooting>Options (from a system administrator account) then removing any IDs you see listed in the Debug Log IDs field. Once removed be sure to save the changes, then flush your browser cache to confirm the warning is no longer being displayed. I hope this helps!

With that being said though, I'd be happy to get a feature request submitted on your behalf to disable this warning at least for a period of time after being dismissed initially. Have a good one!

IMO, this alert should not be closeable and should always be while debug logs are enabled, since it may impact the performance of the server, you should always be alerted they are running just incase you forget or something.

The problem is that we like to keep certain logs permanently on detailed mode, as you never know when you need to go back and diagnose a problem from the past few days.  For example, we tend to have to search the Delivery debug log file quite frequently.

Jonathan, this warning does not apply to the standard logging in SmarterMail, only the debug log IDs you've added here: 

As such, you should be able to set your other standard logging to Detailed without incurring this notification.

Kyle,

I am curious to know though, is it really that much worse to have 1/2 debug logs enabled over running a ton of normal logs set to detailed? I assume it varies depending on which debug log ID(s) you have enabled?

Correct, this would vary quite a bit from log to log and from environment to environment as some servers see more IMAP traffic than anything else, and so naturally their IMAP logs would be quite a bit larger than EAS logs for example. 

Additionally, on the debug log side, some of these logs are significantly more verbose than others like our MAPI debug logging.