How to enable debug logging for advanced troubleshooting of the Premium Antispam feature of Symantec Mail Security for Microsoft Exchange (SMSMSE).
For rules update and missed Spam issues
Note: When set to log level 7, both the bmserver.log and conduit.log will take a significant amount of disk space. Revert these values to defaults as soon as possible after trapping the problem you are troubleshooting.
Locate the section containing:
<program xsi:type="conduitType" name="conduit">
<log enabled="true" level="4" period="1" periodUnits="DAY" numberRetained="30" haltThreshold="500" reduceThreshold="1024">C:\Program Files\Symantec\SMSMSE\<version>\Server\logs\conduit.log</log>
Change the value assigned to "log level" to 7 in order to enable debug logging for the conduit module. The line should now read like:
<program xsi:type="conduitType" name="conduit">
<log enabled="true" level="7" period="1" periodUnits="DAY" numberRetained="30" haltThreshold="500" reduceThreshold="1024">C:\Program Files\Symantec\SMSMSE\<version>\Server\logs\conduit.log</log>
For troubleshooting the engine/server module
Locate the section containing:
<program xsi:type="bmserverType" name="bmserver">
<log enabled="true" level="4" period="1" periodUnits="DAY" numberRetained="30" haltThreshold="500" reduceThreshold="1024">C:\Program Files\Symantec\SMSMSE\<version>\Server\logs\bmserver.log</log>
Change the value assigned to "log level" to 7 in order to enable debug logging for the bmserver module. The line should now read like:
<program xsi:type="bmserverType" name="bmserver">
<log enabled="true" level="7" period="1" periodUnits="DAY" numberRetained="30" haltThreshold="500" reduceThreshold="1024">C:\Program Files\Symantec\SMSMSE\<version>\Server\logs\bmserver.log</log>
The logs are located at:
c:\Program Files\Symantec\SMSMSE\<version>\Server\logs
NOTE: Replace
Log Level Information
Logging Level
|
Logging Level Name
|
1
|
|
2
|
|
3
|
Errors
|
4
|
Warnings
|
5
|
Notices
|
6
|
Information
|
7
|
Debug
|
CAUTION: Make sure to turn the debugging off as these logs can take up a very large amount of space if left running. After submitting the requested logs to support, you can remove the log file to free up disk space.