How to enable debug logging on the Premium AntiSpam module for Symantec Mail Security for Microsoft Exchange

Article:TECH90511  |  Created: 2008-01-13  |  Updated: 2014-06-30  |  Article URL http://www.symantec.com/docs/TECH90511
Article Type
Technical Solution


Issue



You need to troubleshoot a problem you think is related to Premium AntiSpam, therefore you'll need to debug the module.


Solution



  1. Stop the Symantec Mail Security for Microsoft Exchange service.
  2. Stop the Symantec Mail Security Utility Service.
  3. Open the following file in an editor:

    Default location:

    32-bit OS: c:\Program Files\Symantec\SMSMSE\<version>\Server\SpamPrevention\bmiconfig.xml
    64-bit OS: c:\Program Files (x86)\Symantec\SMSMSE\<version>\Server\SpamPrevention\bmiconfig.xml

    NOTE:  Replace <version> with the version of SMSMSE installed.

    The following is an example for 6.5 on 64-bit OS:

    c:\Program Files (x86)\Symantec\SMSMSE\6.5\Server\SpamPrevention\bmiconfig.xml

     
  4. Change the file as directed below.
  5. Start the Symantec Mail Security for Microsoft Exchange service.
  6. Start the Symantec Mail Security Utility Service.


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 level="4" period="1" periodUnits="DAY" numberRetained="30">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 level="7" period="1" periodUnits="DAY" numberRetained="30">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 level="4" period="1" periodUnits="DAY" numberRetained="30">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 level="7" period="1" periodUnits="DAY" numberRetained="30">C:\Program Files\Symantec\SMSMSE\<version>\Server\logs\bmserver.log</log>



The logs are located at:

32-bit OS: c:\Program Files\Symantec\SMSMSE\<version>\Server\logs
64-bit OS: c:\Program Files (x86)\Symantec\SMSMSE\<version>\logs

NOTE:  Replace <version> with the version of SMSMSE installed.

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. 
  



Legacy ID



2008101314044654


Article URL http://www.symantec.com/docs/TECH90511


Terms of use for this information are found in Legal Notices