orangeuf.blogg.se

This is important while troubleshooting a problem. MailEssentials supports different logging levels, however only Log Level ‘1’ is implemented The following table provides an explanation of the parts (columns) that are mostly used for troubleshooting: Refer to this linked article on Reading Email Headers to extract the Message-ID.Īll the debug log files have the same standard format, which is shown below: Date, Time, Millisec., Log Level, Process ID, Thread ID, Event Type, Source, Description

Format of the Debug logsĪll debug logs differentiate emails using the Message-ID, so when troubleshooting a problem using the debug logs, it is important that we get an email showing the problem and that it contains the email header information. Others, like the MTA debug log file, has had its limit increased to 10Mb. Some debug log files have a limit of less than 5Mb. When the log file reaches again 5Mb, the. When this limit is reached, the log file is saved to a. Most of the debug log files have a limit of 5Mb. \GFI\MailEssentials\Attendant\DebugLogs\.\GFI\MailEssentials\ActionServices\DebugLogs\.\GFI\MailEssentials\EmailSecurity\DebugLogs\.\GFI\MailEssentials\Antispam\DebugLogs\.When Debugging is enabled, all the debug log files from the various MailEssentials components are saved to the following locations: Debugging tends to slow down performance and to create unnecessary logging that will take disk space.

Note: It is recommended that debugging is switched off after retrieving the debug files required. After the ‘ Debug’ value has been changed to ‘1’, the GFI MailEssentials services and the Microsoft Exchange Transport service need to be restarted. After the ‘ Debug’ value has been changed to ‘1’, the GFI MailEssentials services and the IIS Admin service will have to be restarted.įrom the Registry on 圆4 systems: Start > All Programs > GFI MailEssentials > GFI MailEssentials Switchboard > Tracing Tab and Select Tracing enabled by ticking the checkbox.įrom the Registry on x86 systems: Description Enabling Debug logging in MailEssentialsĭebug logging for all the modules in MailEssentials can be enabled from the MailEssentials Switchboard or the Windows registry. The next section explains the various debug logs that are created by MailEssentials, how to enable extended debugging, and the format of the debug logs. You can enable or disable debug logging by following the steps outlined in this linked article: How can I enable or disable debug logging in GFI MailEssentials? Use tracing for troubleshooting purposes or when contacting GFI Support. MailEssentials provides the facility of creating log files for debugging purposes. This article explains the various debug logs that are created by MailEssentials, how to enable extended debugging, and the format of the debug logs.