Defining the symbol in this way allows you to use the /DATABASE qualifier and specify (one-host) commands on the command line.

By default, REJMAN loads in the current configuration file, MX_DIR:MX_REJECTION_DATABASE.MXCFG, when started. REJMAN requires the SYSLCK privilege to be able to lock the rejection database from being modified by other processes. (/DATABASE=file-spec) Loads the specified rejection database for editing. If not specified, the default database, MX_DIR:MX_REJECTION_DATABASE.MXCFG, is loaded. (Command Input Redirection\\rejman_cmd_redirect) Execute REJMAN commands stored in a file. (@) (file-spec) (file-spec) Name of the file containing REJMAN commands. If the file type is omitted, the default type is MCP. Use this command to have REJMAN take further command input from the specified file. There is no built-in limit on the number of levels of nesting of command files, so be careful when using input redirection from within a command file.

This command can only be used at the REJMAN command prompt, not as a (one-shot) REJMAN command. To have a file be used for input for an entire REJMAN session, use the following sequence of DCL commands. ($ )(DEFINE/USER SYS$INPUT file-spec) ($ )(REJMAN) (ADD EXCLUSION\\rejman_cmd_add_excl) Adds an exclusion to heuristic junk mail filters. (ADD EXCLUSION) (sender-pat) (/HEURISTIC=heuristic-name\) (sender-pat) E-mail address or wildcard pattern to match the sender of the message, as it would appear in either the RFC822 From header or the SMTP MAIL FROM command. This command adds a new exception to one or all of the heuristic filters. If the sender (from either the RFC822 From header, or the SMTP MAIL FROM return path) of a message matches this address or pattern, the message is excluded from the specified heuristic filter check (or all checks if the /HEURISTIC qualifier is omitted). (/HEURISTIC=heuristic-name) Specifies the heuristic filter to which this exclusion applies. If not specified, the exclusion is added to the global exclusion list for all heuristic filter checks. (ADD REJECTION\\rejman_cmd_add_rej) Adds a rejection rule to the database for the SMTP server. (ADD REJECTION) (sender-pat [rcpt-pat]) (/ACCEPT[=accept-kwd]\) (/ADDRESS=ip-addr-pat\) (/FORWARD_TO=address\) (/HEADER\) (/MESSAGE=rejection-message\) (/REGEX\) (sender-pat) E-mail address or wildcard pattern to match the sender of the message, as it would appear in the SMTP MAIL FROM command. If the /HEADER qualifier is specified, this parameter is treated as a wildcard pattern to match an RFC822 header in the message, and the (rcpt-pat) parameter and other qualifiers are not used. (rcpt-pat) E-mail address or wildcard pattern to match the recipient of the message, as it would appear in the SMTP RCPT TO command. If omitted, matching only occurs against the sender, and a match causes the rejection to happen immediately after receipt of the MAIL FROM command, rather than on a per-recipient basis.

To match a character normally regarded as a wildcard (asterisk or percent sign), prefix the character with a backslash.

This parameter is not permitted if the /HEADER qualifier is specified. This command adds a new rejection rule to the database. For address-based rejection rules (those not specifying /HEADER), a match occurs for any of the following: (NUMBERED) (sender-pat) is specified with no (rcpt-pat), and the address in the SMTP MAIL FROM command matches the specified address or pattern. The sending system is notified of the rejection in the status code returned for the MAIL FROM command. (sender-pat) and (rcpt-pat) are both specified. In this case, the SMTP MAIL FROM address must match (sender-pat) and the RCPT TO address must match the (rcpt-pat). The check occurs on receipt of the RCPT TO command, and if a match occurs, the sending SMTP system is notified of the rejection in the status returned on the RCPT TO. Note that this may not prevent the delivery of the message to other users who do not match the (rcpt-pat) pattern. In both cases, the rule can be restricted by the use of the /ADDRESS qualifier; if specified, the sending SMTP system's numeric IP address must match the address or pattern specified on that qualifier. You may modify the behavior of MX's SMTP server when a match occurs by using other qualifiers; see the qualifier descriptions for more information.

Header-based rules are specified with the /HEADER qualifier. Header-based rules are checked only after the entire message is received by the SMTP server, and if a match occurs, the sender is notified of the rejection after it transmits the termination sequence (CRLF-dot-CRLF) for the message. Header-based rules affect delivery to all specified recipients of a message; the (rcpt-pat) parameter is not used. Other qualifiers are not allowed when the /HEADER qualifier is used. (/ACCEPT[=accept-kwd]) Specifies that the message should be accepted rather than rejected. This qualifier can be used to provide exceptions to other rejection rules; it applies only when both the (sender-pat) and (rcpt-pat) parameters are specified. Valid values for (accept-kwd) are: (unnumbered) (AS_IS\BOLD). This is the default when no keyword is specified, and indicates that the recipient address should not be altered. (REWRITE=\BOLD)(new-rcpt-addr). This indicates that the recipient's address should be rewritten to the specified new address. This mechanism can be used to re-direct messages that would otherwise be rejected to the postmaster or to another party that might be interested in tracking the unwanted messages. This qualifier cannot be used in combination with the /MESSAGE qualifier or the /HEADER qualifier. (/ADDRESS=ip-addr-pat) Specifies either an IP address (in dotted-decimal form) or a wildcard pattern for matching an IP address. If specified, the IP address of the sending SMTP system is obtained for the incoming connection and matched against the specified address or pattern. This qualifier is not allowed when /HEADER is specified. (/FORWARD_TO=address) Specifies an e-mail address to which a message rejected by a header-based rule should be forwarded. This qualifier is used only with the /HEADER qualifier. When a message is forwarded using this qualifier, additional headers are included with the diverted message to indicate the original list of recipients for the message. (/HEADER) Modifies the type of rejection rule to be based on RFC822 headers, rather than on SMTP envelope addresses. When specified, the (sender-pat) parameter is used for matching RFC822 headers that might be present in the incoming message, and no other parameters or qualifiers are allowed. (/MESSAGE=rejection-message) Specifies the message emitted by the SMTP server which accompanies the SMTP status code indicating that the MAIL FROM or RCPT TO command has been rejected. By default, a generic message is emitted, indicating that rejection for the sender or recipient has been programmed. You cannot use this qualifier with either the /HEADER qualifier or the /ACCEPT qualifier. (/REGEX) Specifies that the sender/recipient pattern, or header text pattern, uses regular expressions instead of VMS-style wildcards. For header matching, specify /REGEX after the /HEADER qualifier. (ATTACH\\rejman_cmd_attach) Transfers control to another process in the current process tree. (ATTACH) ([process-name]) (/IDENTIFICATION=process-id\) (/PARENT\) (process-name) Name of the process to which the terminal should be attached. The process must be in the current process tree. This parameter is omitted if one of the qualifiers is specified. This command is similar to the DCL ATTACH command. It is used in interactive jobs to attach the terminal to another process in the current process tree for the job. (/IDENTIFICATION=process-id) Specifies the process by its process identification, a hexadecimal number. (/PARENT) Specifies that the terminal should be attached to the current subprocess's immediate parent in the process tree. (CHECK\\rejman_cmd_check) Checks to see if an address would be blocked by the rejection rules. (CHECK) (sender-address [recipient-address]) (/ADDRESS=ip-address\) (sender-address) An e-mail address as it would appear on an SMTP MAIL FROM: command, representing the sender of the message. (recipient-address) An e-mail address as it would appear on an SMTP RCPT TO: command, representing the message recipient. If not specified, only the sender address will be checked. This command simulates the check performed by the SMTP server on a sender address, optionally combined with a recipient address and the numeric IP address of a host.

CHECK will signal its success or failure in finding a matching rule. If successful, the patterns in the rule are displayed in the message. (/ADDRESS=ip-address) Specifies the IP address to be used in the rejection check. This should be specified in dotted-decimal format. (DEFINE/KEY\\rejman_cmd_defkey) Defines an equivalence string and a set of attributes with a key on the terminal keyboard. (DEFINE/KEY) (key-name equivalence-string) (/ECHO\) (/ERASE\) (/IF_STATE\) (/LOCK_STATE\) (/LOG\) (/SET_STATE\) (/TERMINATE\) See the DCL help entry for DEFINE/KEY for more information on this command.

You can have a set of keys defined automatically for use with REJMAN by placing DEFINE/KEY commands in the file SYS$LOGIN:MX_MCP_KEYDEFS.INI. Note that this is the same file that is used with the MCP program. (DELETE EXCLUSION\\rejman_cmd_del_excl) Removes an exclusion from heuristic junk mail filters. (DELETE EXCLUSION) (sender-pat) (/HEURISTIC=heuristic-name\) (sender-pat) E-mail address or wildcard pattern to match the sender of the message, as it would appear in either the RFC822 From header or the SMTP MAIL FROM command. This command removes an entry from either the global exclusion list, or from the exclusion list for a specific heuristic filter. If the sender (from either the RFC822 From header, or the SMTP MAIL FROM return path) of a message matches this address or pattern, the message is excluded from the specified heuristic filter check (or all checks if the /HEURISTIC qualifier is omitted). (/HEURISTIC=heuristic-name) Specifies the heuristic filter to which this exclusion applies. If not specified, the matching entry is removed from the the global exclusion list for all heuristic filter checks. (DELETE REJECTION\\rejman_cmd_delrej) Removes a rejection rule from the database. (DELETE REJECTION) (sender-pat [rcpt-pat]) (/ADDRESS=ip-addr-pat\) (/HEADER\) (/IDENTIFIER=rule-id\) This command deletes a rule from the rejection database. Deletion occurs when the specified parameters and qualifiers match the values used when the rule was added. (/ADDRESS=ip-addr-pat) Specifies either an IP address (in dotted-decimal form) or a wildcard pattern for matching an IP address. This qualifier is not allowed when /HEADER or /IDENTIFIER is specified. (/HEADER) Modifies the type of selected rejection rule to be based on RFC822 headers, rather than on SMTP envelope addresses. (/IDENTIFIER=rule-id) Selects the rule to be deleted based on its unique identifier, an integer value assigned when the rule is added to the rejection database. (DISABLE HEURISTIC\\rejman_cmd_disable_heuristic) Disables junk mail heuristic filters in the SMTP server. (DISABLE HEURISTIC) ([heuristic-name...]) (/ALL\) (heuristic-name) A comma-separated list of one or more keywords that identifies the heuristic filters to be disabled. See the help for ENABLE HEURISTIC (rejman_cmd_enable_heuristic) for the list of heuristic filter names. This command disables one or more of the heuristic junk mail filters. (/ALL) Disables all heuristic filters. No parameters are permitted when this qualifier is specified. (ENABLE HEURISTIC\\rejman_cmd_enable_heuristic) Enables junk mail heuristic filters in the SMTP server. (ENABLE HEURISTIC) ([heuristic-name...]) (/ALL\) (/CONFIDENCE_LEVEL={DEFAULTclevel}\) (heuristic-name) A comma-separated list of one or more of the following keywords which identify the heuristics to be enabled: (UNNUMBERED) FROM_TO_SENDER_SAME INVALID_AOL_ADDRESS INVALID_FROM INVALID_HOTMAIL_ADDRESS INVALID_TO MSGID_HAS_FROM MSGID_HAS_TO NULL_FROM NULL_MSGID NULL_TO NUMERIC_ADDRESS PRECEDENCE_BULK RECEIVED_AFTER_FROM RECEIVED_ALL_ZEROS UIDL_AUTH_SENDER X_UIDL This command enables one or more of the heuristic junk mail filters. (/ALL) Enables all heuristic filters. No parameters or other qualifiers are permitted when this qualifier is specified. (/CONFIDENCE_LEVEL={DEFAULTclevel}) Specifies the confidence level to be associated with a match against this filter. This is a local qualifier that must be specified immediately after a heuristic name.

The confidence level for a filter is a number representing the likelihood that a message matching that filter is junk mail. A low confidence level indicates that the message is more likely to be legitimate; a high confidence level indicates that the message is more likely to be junk mail. Each message passed through the heuristic filters is assigned the highest possible confidence level for each filter it matches, until either all enabled filters are checked or the message is given a confidence level that is greater than the REJECT level set with the SET HEURISTIICS command.

If the DEFAULT keyword is specified, the built-in default confidence level for the heuristic is set. Otherwise, specify a decimal number from 0 through 10 to set a non-default confidence level. (EXIT\\rejman_cmd_exit) Saves changes to the database and exits the program. (EXIT) ( ) This command saves the changes made during the current REJMAN session and exits the program. (HELP\\rejman_cmd_help) Displays information about REJMAN commands. (HELP) ([topic]) (topic) Topic, such as a REJMAN command, about which you want help. If omitted, a list of available commands is displayed. This command displays descriptions and other information on REJMAN commands. (QUIT\\rejman_cmd_quit) Exits the program without saving changes. (QUIT) ( ) This command causes the program to exit without saving the changes made during the current session. You will be prompted for confirmation if you have made any changes. (PURGE\\rejman_cmd_purge) Purges old rejection rules from the database. (PURGE) () (/BEFORE=date-time\See text.) (/[NO]LOG\/LOG) The PURGE command deletes rejection rules from the database considered (old;) that is, they were last used by the SMTP server to reject messages before a date in the past. By default, rules not used for 30 days are purged from the database; you may override this by specifying the /BEFORE qualifier. (/BEFORE=date-time) By default, the PURGE command deletes records that have not been used for 30 days. You may override this cut-off date with the /BEFORE qualifier. (/LOG) By default, the PURGE command logs a message indicating the number of rules purged from the database, along with the cut-off date when successful. Specify /NOLOG to prevent this message from being issued on a successful PURGE. (SAVE\\rejman_cmd_save) Writes out the rejection database to a file. (SAVE) ([file-spec]) (file-spec) Name of the file to which the database should be written. If omitted, the default is MX_DIR:MX_REJECTION_DATABASE.MXCFG, or the file pointed to by the logical name MX_REJECTION_DATABASE. This command writes the rejection database to a file. To ensure that the MX SMTP server uses the rejection database information, omit the file specification to allow REJMAN to write the information to the default location. (SET HEURISTICS\\rejman_cmd_set_heur) Modifies global settings for the heuristic junk mail filters. (SET HEURISTICS) ( ) (/CONFIDENCE_LEVEL=[(ACCEPT=(number),REJECT=(number))]\) (/[NO]INCLUDE_REASON\/NOINCLUDE_REASON) (/REJECT_ACTION={DROPFORWARD=(address)}\) This command modifies the global settings for the heuristic junk mail filter in the SMTP server. (/CONFIDENCE_LEVEL) Sets the confidence levels for accepting and rejecting messages as junk mail. Each heuristic filter has a confidence level, representing the likelihood that a message matching that filter is junk mail. This qualifier is used to set the thresholds for accepting a message as legitimate and rejecting a message as junk mail.

This qualifier takes a list of keywords (ACCEPT, REJECT) that assign the threshold values. Each keyword must be specified with a value, which is either a number from 0 to 10 or the keyword DEFAULT. If you specify both the ACCEPT and REJECT keywords, you must enclose the list in parentheses.

The default settings are: /CONFIDENCE_LEVEL=(ACCEPT=0,REJECT=8) A message is considered fully acceptable when its assigned confidence level is (less than or equal to) the ACCEPT threshold; in that case, the message is passed on to recipients with no further action. A message is considered junk mail when its assigned confidence level is (greater than) the REJECT threshold; in that case, the action specified by SET HEURISTICS/REJECT_ACTION is taken.

Messages assigned confidence levels (between) the two thresholds are considered partially acceptable. They are passed on to the recipients with an additional header (X-Junk-Mail-Rating) warning them that the message may be junk mail. A second additional header containing the reason for the warning may also be included based on the SET HEURISTICS/INCLUDE_REASON setting. (/INCLUDE_REASON) For a message that is assigned a confidence level that falls between the ACCEPT and REJECT thresholds, specifies that an additional header (X-Junk-Mail-Reason) be included in the message to explain to the recipient why the message was flagged with a warning indicating that it might be junk mail. The default is /NOINCLUDE_REASON. (/REJECT_ACTION) Specifies the action to take when the confidence level assigned to a message exceeds the REJECT threshold. This qualifier takes one of two keyword values. The DROP keyword specifies that the SMTP server should drop the message by sending an error status back to the sending SMTP system. The FORWARD keyword specifies that the message should be diverted to a different address. You must specify an e-mail address as a value for the FORWARD keyword.

When the FORWARD keyword is specified, the message is silently diverted to the forwarding address, with headers added to the top of the message indicating the reason the message was rejected, the original sending address, and the original recipients for the message. This setting is provided so that the local postmaster or other responsible person can verify that any messages rejected by the heuristic filters are in fact junk mail. In the case that a rejected message is actually legitimate, the system manager can then forward the message on to its intended recipients and modify the heuristic filter configuration to prevent such messages from being rejected in the future.

The default setting is /REJECT_ACTION=DROP. (SHOW\\rejman_cmd_show) Displays rejection entries and other information. (SHOW) (keyword) (/COMMAND\) (/IDENTIFIER=rule-id\) (/OUTPUT=file-spec\) (keyword) Specifies the information to be shown. Acceptable keywords are ALL, DATABASE_FILE, HEURISTICS, KEY, REJECTIONS, and VERSION. You must specify one of these keywords. SHOW DATABASE_FILE displays the name of the database file that you are modifying.

SHOW HEURISTICS displays information about the heuristic filters and exclusions.

SHOW KEY displays key definitions. Refer to the DCL SHOW KEY command for further information.

SHOW REJECTIONS displays the entries in the rejection database, inculding their reference counts, the date and time they were entered in the database, and the date and time they were last used by the SMTP server.

SHOW VERSION displays the version of MX running on the system.

SHOW ALL shows all of the information mentioned above. (/COMMAND) Formats the output as REJMAN commands. This can be used with the /OUTPUT qualifier to create a REJMAN command file to re-create the rejection database from scratch. (/IDENTIFIER=rule-id) Used only with SHOW REJECTIONS, this qualifier selects the rejection rule to be displayed by its unique identifier, an integer value. If not specified, all rejection rules are displayed. (/OUTPUT=file-spec) Directs the displayed information to the specified file. By default, output is displayed on the current standard output device (based on the SYS$OUTPUT logical name). (SPAWN\\rejman_cmd_spawn) Spawns a subprocess. (SPAWN) ([dcl-command]) (dcl-command) A DCL command to be executed in the subprocess. If omitted, REJMAN is suspended and the terminal is attached to the subprocess for interactive entry of commands. To return to the process running REJMAN, use the DCL LOGOUT command to end the subprocess. This command creates a subprocess to execute one or more DCL commands. See the description of the DCL SPAWN command for further information.