HP OpenVMS Systems Documentation

To monitor the mail queues, examine the TCPIP$SMTP_LOGFILE.LOG and the TCPIP$SMTP_RECV_RUN.LOG files.

18.4.2 Changing the Number of Mail Queues

To change the number of SMTP queues, follow these steps:

1. Stop SMTP and MAIL on the root node by entering the following commands:

   TCPIP> DISABLE SERVICE SMTP TCPIP> STOP MAIL

2. Change the SMTP configuration by entering the following command:

   TCPIP> SET CONFIGURATION SMTP/QUEUES=new_number

   
   The maximum number of queues set with this command is 10.
3. Restart SMTP and MAIL by entering the following commands:

   TCPIP> START MAIL TCPIP> ENABLE SERVICE SMTP

To display SMTP routing information, use the SHOW MX_RECORDS command. If you omit destination from the command line, you see the entries in the local MX database.

If you specify destination, you see all the entries in all the databases that the SMTP mailer would look at, if necessary, to route mail to the destination. The local MX database and the DNS MX database are usually as far as TCP/IP Services needs to search.

18.4.4 SMTP Logging

SMTP logs mail queue and mail symbiont events to the following files:

• TCPIP$SMTP_LOGFILE.LOG
• TCPIP$SMTP_RECV_RUN.LOG

The symbiont and receiver contain a feature called snapshot logging, which allows you to run with full diagnostics enabled but to write the diagnostics to the log file only if an error is signaled. This feature saves disk space and allows the receiver or the symbiont, or both, to run at a normal speed. As each line of diagnostic text is generated, it is saved in an internal snapshot buffer rather than to the disk. The buffer is circular in that once it fills up, new lines of text start to overwrite the old data already there. This functionality provides a snapshot of the last lines of diagnostic text.

Logical names are available to modify the way SMTP logs information and the type of information it reports. These are described in Section 18.5.

18.4.5 Starting and Stopping SMTP

SMTP consists of two components: the sender (the queuing mechanism) and the receiver. You must start the sender before enabling the receiver. The receiver is activated by the auxiliary server.

The SMTP can be shut down and started independently. This is useful when you change parameters or logical names that require the service to be restarted.

The following files are provided:

• SYS$STARTUP:TCPIP$SMTP_STARTUP.COM allows you to start up the SMTP independently.
• SYS$STARTUP:TCPIP$SMTP_SHUTDOWN.COM allows you to shut down the SMTP independently.

To preserve site-specific parameter settings and commands, create the following files. These files are not overwritten when you reinstall TCP/IP Services:

• SYS$STARTUP:TCPIP$SMTP_SYSTARTUP.COM can be used as a repository for site-specific definitions and parameters to be invoked when the SMTP is started.
• SYS$STARTUP:TCPIP$SMTP_SYSHUTDOWN.COM can be used as a repository for site-specific definitions and parameters to be invoked when the SMTP is shut down.

The SMTP services can be started automatically using the TCPIP$CONFIG configuration procedure, or manually using the following command:

$ @SYS$STARTUP:TCPIP$SMTP_STARTUP.COM

To stop SMTP, enter:

$ @SYS$STARTUP:TCPIP$SMTP_SHUTDOWN.COM

You can modify the SMTP configuration by defining logical names that are translated at queue startup time. Characteristics you can control include:

• Event-and error-logging diagnostics
• How mail headers are displayed
• How mail is routed
• How SMTP interacts with OpenVMS Mail

To store the settings of logical names, include the DEFINE command in one of the following command procedures:

• SYS$STARTUP:TCPIP$SMTP_SYSTARTUP.COM, for setting logicals when SMTP starts up
• SYS$STARTUP:TCPIP$SMTP_SYSHUTDOWN.COM, for setting logicals when SMTP shuts down

When you redefine the value of a logical, you must restart SMTP. Use the following command procedures to shut down and restart SMTP:

• SYS$STARTUP:TCPIP$SMTP_STARTUP.COM
• SYS$STARTUP:TCPIP$SMTP_SHUTDOWN.COM

For more information, see Section 18.4.5.

18.5.1 Defining SMTP Logical Names

Each SMTP logical name changes a configuration setting for handling SMTP mail operations. Some SMTP logical names enable or disable configuration options. If you define the logical name, the option is considered to be enabled. If the logical name is not defined, the option is disabled.

To disable this type of configuration option, simply remove the logical name.

To define this type of logical, set its value to 1.

For example, to enable message logging for messages received from SMTP clients, define the TCPIP$SMTP_RECV_TRACE as follows:

$ DEFINE/SYSTEM TCPIP$SMTP_RECV_TRACE 1

Other logical names require that you supply a value. For example, to enable logging that provides information about symbiont activity during control file processing, define the logical name TCPIP$SMTP_LOG_LEVEL with a value of 3. For example:

$ DEFINE/SYSTEM TCPIP$SMTP_LOG_LEVEL 3

SMTP consists of three main components:

• Receiver
• Symbiont
• MAIL$PROTOCOL (used to communicate with OpenVMS Mail)

Each logical name can be used by one or more of the SMTP components.

18.5.2 SMTP Logical Names

Table 18-4 lists the SMTP logical names and, for each, describes the purpose, valid settings, and components that use it.

send buf=MAIL FROM:<jones@acme.com>\d\a

recv buf=250 <jones@acme.com>... Sender OK\d\a

 $ DEFINE/SYSTEM TCPIP$SMTP_LOG_LEVEL 5

 $ DEFINE/SYSTEM TCPIP$SMTP_SYMB_SNAPSHOT_BLOCKS 200

 $ DEFINE/SYSTEM TCPIP$SMTP_RECV_DEBUG 1

 $ DEFINE/SYSTEM TCPIP$SMTP_RECV_TRACE 1

 $ DEFINE/SYSTEM TCPIP$SMTP_RECV_SNAPSHOT_BLOCKS 200

$ DEFINE/SYSTEM TCPIP$SMTP_POSTMASTER_ALIAS "Postmaster"

 $ DEFINE/SYS/EXEC TCPIP$SMTP_8BITMIME_HACK 1

SPAM is the Internet equivalent of junk mail and is a growing source of annoyance to Internet users. Antispam is a function of SMTP that is designed to inhibit the transmission of spam.

SMTP Antispam is implemented in the SMTP receiver which, for the purposes of this discussion, is called the SMTP server. The following sections describe how to enable and configure SMTP Antispam.

18.6.1 Enabling and Managing SMTP Antispam

To enable and manage SMTP Antispam, create or edit the following file:

TCPIP$SMTP_COMMON:SMTP.CONFIG

The logical name TCPIP$SMTP_COMMON is defined at TCP/IP Services startup. For more information, see Section 18.5.

The SMTP.CONFIG file should be owned by TCPIP$SMTP and protection should be set to (W:RE).

The file SMTP_CONFIG.TEMPLATE is provided to help you create this file; it contains guidelines on how to configure Antispam.

For guidelines about specifying configuration options in the SMTP.CONFIG file, see Section 1.1.5.

18.6.1.1 SMTP Antispam Field Names

Table 18-5 describes the field names and values for Antispam configuration.

.

The following sections provide further information about the configuration options.