Use one of the following steps to verify that the Messaging Server MTA is functioning properly.
Run the imsimta test -rewrite command on a sample local user address. There should be no errors. For example:
# /opt/SUNWmsgsr/sbin/imsimta test -rewrite -debug=level=4 -filter user99@red.example.com 12:32:29.33: - passed. 12:32:29.33: - send_access mapping check: l|postmaster@host1.red.example.com|ims-ms|user99@ims-ms-daemon 12:32:29.33: Mapping 4 applied to |postmaster@host1.red.example.com|ims-ms|user99@ims-ms-daemon 12:32:29.33: Final result "l|postmaster@host1.red.example.com|ims-ms|user99@ims-ms-daemon" 12:32:29.33: - passed. 12:32:29.33: - adding address user99@ims-ms-daemon to channel ims-ms 12:32:29.33: Closing URL context 1, new type = 7 12:32:29.33: - adding address user99@red.example.com to headers. 12:32:29.33: Copy estimate after address addition is 2 *** Expanded address: user99@red.example.com Submitted address list: ims-ms user99@ims-ms-daemon (orig user99@red.example.com, inter user99@red.example.com, host ims-ms-daemon) *NOTIFY-FAILURES* *NOTIFY-DELAYS* Submitted notifications list: |
Compose and send an email. Look at the Symantec Brightmail server logs under the /var/log/brightmail directory and verify that the bmserver_logs file contains information about this message.
You can also log in to the Control Center and check for statistics.
If you set SPAMFILTER1_OPTIONAL=-2 in the option.dat file, as previously explained, then you can check for warning syslog messages to verify the MTA/Symantec Brightmail operation.
If you set LOG_FILTER=1 in the option.dat file, you can check that “expected” results are showing up in the filter field in mail.log* records. See Adding More Information to Message Transaction Records for more information.