Configuring Brightmail with Sun Java System Messaging Server

ProcedureTo Modify the option.dat and imta.cnf Files

  1. Modify the option.dat file as follows.

    Here the Symantec Brightmail client is located under the /SYMSDK/BSDK directory.


    !
    ! Brightmail Stuff
    !
    spamfilter1_config_file=/SYMSDK/BSDK/etc/bmiconfig_client.xml
    spamfilter1_library=/SYMSDK/BSDK/lib/libbmiclient.so

    Consider also setting SPAMFILTER1_OPTIONAL=-2 (or SPAMFILTERn_OPTIONAL=-2, as appropriate) in the option.dat file. If the MTA encounters an error contacting Symantec Brightmail, then in addition to temporarily rejecting incoming SMTP messages, the MTA will also generate a syslog notice. For syslog notices to be routed appropriately, you might also need to adjust the SNDOPR_PRIORITY option.dat option and your syslog.conf file.

  2. Modify the imta.cnf file as follows.

    Symantec Brightmail scanning can be selected in the MTA in a variety of ways, including via use of a per-user LDAP attribute, or via use of a per-domain LDAP attribute, or according to source or destination channel. A typical usage is to perform Symantec Brightmail scanning on all messages destined to locally hosted users: that is, on all messages being delivered to users via an ims-ms channel, or via tcp_lmtp* client channels. For instance, to trigger Symantec Brightmail “spam” filtering on all messages being delivered to the store via the ims-ms channel, if Symantec Brightmail is being used as spam/virus filter package # 1, add destinationspamfilter1optin spam to the ims-ms channel definition in the imta.cnf file. Such a channel definition might then look something like the following:


    ! ims-ms
    ims-ms defragment subdirs 20 notices 1 7 14 21 28 \
     backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" \
     maxjobs 2 pool IMS_POOL fileinto $U+$S@$D \
     destinationspamfilter1optin spam
    ims-ms-daemon
  3. Compile the MTA configuration.

    ./imsimta cnbuild

  4. Restart the MTA dispatcher.

    imsimta restart dispatcher

    This will cause use of the new compiled configuration (enabling Symantec Brightmail use) by the MTA's (new) SMTP server processes.