3.6.6 MAILbus 400 Message Router Gateway (XMR)

This section describes how to use the module-specific sections of the initialization file to configure a scanning module for the MAILbus 400 Message Router Gateway.

3.6.6.1 The Message_Severity Section

This section specifies different severity value for problems revealed during hard-coded checking. It has the following format:

[Message_Severity]

You can specify the following:

• Cannot_check_body_part=error_level

  The command to check bodypart cannot be started.

• Cannot_get_xmr_information=error_level

  The scanning module is unable to retrieve information about XMR gateway using NCL.

• Cannot_get_XMR_Routing=error_level

  The scanning module is unable to get XMR routing information using NCL.

In all cases, the value error_level is the severity code for message severity,as defined in the note at the beginning of Section 3.3.

For example:

[Message_Severity]
Cannot_check_body_part=3
Cannot_get_xmr_information=4
Cannot_get_XMR_Routing=3

3.6.6.2 The XMR_Routing Section

This section specifies the command to use to check Routing Instructions, and the severity values for errors that the scanning module returns. It has the following format:

[XMR_Routing]

You can specify the following:

• command=command

  A mandatory parameter that gives the NCL command used to get the routing information. The default value is:

  RUN SYS$SYSTEM NCL SHOW MTS %S ORADDRESS %S ROUTING INSTRUCTION
  

• Bad_Action=error_level

  An action does not match the domain specified in the `Transfer to domain' clause.

• Bad_Domain=error_level

  The domain name specified for the MAILbus 400 Message Router Gateway is not the XMR domain specified in NCL.

In both cases, the value error_level is the severity code for message severity, as defined in the note at the beginning of Section 3.3.

For example:

[XMR_Routing]
command=RUN SYS$SYSTEM NCL SHOW MTS %S ORADDRESS %S ROUTING INSTRUCTION
Bad_Action=3
Bad_Domain=2

3.6.6.3 The XMR_TranslationTable Section

This section specifies whether the scanning module should check the translation table. It has the following format:

[XMR_TranslationTable]

You can specify the following:

• Enable=0|1

  1 enables translation table checking, 0 disables it.

• Severity=error_level

  The severity value for a problem, as defined in the note at the beginning of Section 3.3.

For example:

[XMR_TranslationTable]
Enable=1
Severity=2

3.6.6.4 The Bodypart Mapping Table Section

This section specifies the MAILbus 400 Message Router Gateway's bodypart mapping table. It has the following format:

[Bodypart Mapping Table]

The truncated messages are compared in reverse order of the list you specify.

You must specify the following:

• Command=command

  The command to use to check the XMR bodypart mapping table. The default value is RUN SYS$COMMON:[XMR$]XMR$XBMT_ CHECK.EXE .

• command_message=severity>message

  This defines, for the command_message returned by the command specified, which message and severity the Mail Monitor reports. The command_message is the truncated but meaningful message that the scanning module has received.

For example:

[Bodypart Mapping Table]
Command=RUN SYS$COMMON:[XMR$]XMR$XBMT_CHECK.EXE
XMR-S=2>Bodypart seems ok       4
XMR-E=4>Unknown errors        3
XMR-S-XBMTVERIFIED=0>Bodypart ok      2
XMR-E-XBMTBADSYN=3>Syntax error in bodypart file    1

This example explicitly issues the default command for checking the bodypart mapping table, and then returns are checked in reverse order:

1. XMR-E-XBMTBADSYN is explicitly checked first, leaving other -E- messages until after the explicit verification of the bodypart mapping table in check 2 (XMR- S-XBMTVERIFIED ).

1. XMR-E shows that something undefined is wrong. Thus, an error such as XMR-E-ERROR will generate a message `Unknown errors' with severity of 4 (fatal). Note that, in this case, the 4 represents the severity of the error shown in Mail Monitor's monitor record

2. This and check 2 confirms that the bodypart itself is well-formed.