Troubleshooting the Configuration

Use the following to troubleshoot problems with your configuration.

• If there is a problem in bringing up Symantec Brightmail server, check the Symantec Brightmail log file for errors. If the log file is not displaying errors, then there is a permission problem (write permission problem to the log file). If necessary, for troubleshooting problems, you can change the log level from the default of 4 to log level 7. Level 7 should be used for debugging only. Leaving the debug level at 7 at all times will decrease performance.

  Modify the bmiconfig.xml file under the /opt/symantec/sbas/Scanner/etc directory to change the log level from the default value of 4 to 7. Also, modify the bmiconfig_client.xml file in the /opt/symantec/sbas/Scanner directory to change the log level from 4 to 7.

• If there is a problem with either Symantec Brightmail itself, or with the integration configuration, check the following:

  If the global MTA option (that is, option.dat option) SPAMFILTERn_OPTIONAL is set to -2 or 2, then trouble getting a result back from the nth spam/virus filter package will result in a syslog notice, with syslog facility and severity controlled by the SNDOPR_PRIORITY global MTA option, with text of the general form:

  SPAMFILTERn, error-text

• When Symantec Brightmail is the spam/virus filter package, there is potentially additional information text. If Symantec Brightmail either error location or type information is also available, then the text takes the form:

  SPAMFILTERn, error-text [ - error-location ][ - error-type ]

  where the square bracket characters shown above indicate the optional additional information and are not part of the actual output string. The error-location can be any of client, network, or server; the error-type can be any of memory, network, time-out, data, module down, type arg, or bad version.

  In the case of Symantec Brightmail, the error-text always indicates the stage at which processing failed.

• Enable MM_DEBUG and OS_DEBUG parameters. For example, add the following lines to the option.dat file:

  MM_DEBUG=8 OS_DEBUG=1

  As with Brightmail and high levels of debugging, leaving this level of MTA debugging on is not intended for normal operation and performance once you have solved the problem. Only use this high level of MTA debugging while resolving a problem.

Further Reading

Refer to the Symantec Brightmail AntiSpam documentation at the following location:

http://www.symantec.com/techsupp/enterprise/products/sba/sba_60x/manuals.html

See the following information in the Sun Java System Messaging Server 2005Q4 Administration Guide:

• Chapter 14, Integrating Spam and Virus Filtering Programs Into Messaging Server, in Sun Java System Messaging Server 6 2005Q4 Administration Guide

• Using Symantec Brightmail Anti-Spam in Sun Java System Messaging Server 6 2005Q4 Administration Guide