Technical data

Configuring and Managing the POP Server
18.4 Enabling MIME Mail
18.4 Enabling MIME Mail
The MIME (Multipurpose Internet Mail Extensions) specification provides a set
of additional headers you can use so users can send mail messages composed of
more than simple ASCII text. MIME is an enhancement to RFC 822.
For MIME mail to be decoded correctly, follow these guidelines:
• Configure the SMTP server with the /OPTION=TOP_HEADERS qualifier,
because the first lines of mail text after the four OpenVMS message header
lines and the initial separating line must be the MIME headers.
• Configure the POP server with the TCPIP$POP_IGNORE_MAIL11_
HEADERS logical name. Otherwise, MIME headers are not parsed as
message headers.
• The OpenVMS message
From: field must be recognized as an SMTP address.
Otherwise, the POP server sends the headers it creates from OpenVMS
message headers as the headers of the mail message. For information about
POP message headers, see Section 18.1.6.
Define the logical name TCPIP$SMTP_JACKET_LOCAL to 1 for all SMTP
cluster systems, which ensures that the mail will be delivered if the domain
in the From: or To: fields appears local. For example:
$ DEFINE/SYSTEM TCPIP$SMTP_JACKET_LOCAL 1
If MIME mail does not decode, check the mail headers on the client system. If
you see multiple blocks of headers and the MIME version header is not in the
first block, confirm that you have followed these guidelines.
18.5 Solving POP Problems
The following sections describe ways to troubleshoot problems associated with
using the POP server. Some of these include:
• Reviewing error and OPCOM messages sent to the log file
• Simulating a POP client and entering XTND commands
18.5.1 POP Server Messages
Many of the problems encountered using POP pertain to failed or misinterpreted
commands or authorization errors. As the first step toward solving problems, you
should review the messages provided by the POP server.
The POP server logs command error and OPCOM (authorization) messages in the
file SYS$SYSDEVICE:[TCPIP$POP]POP_RUN.LOG. By default, the POP server
sends informative error messages to the client about specific errors.
If the SERVICE database log option REJECT is set, the POP server sends
OPCOM messages when it rejects POP client commands because of authorization
failures. These errors include the receipt of a client’s USER command with an
invalid user name, or a PASS command with an invalid password.
By default, OPCOM messages are displayed on the client system and are listed in
the log file. To disable OPCOM messages, disable the REJECT logging option for
the POP service, as follows:
$ TCPIP SET SERVICE POP/LOG=NOREJECT
18–12 Configuring and Managing the POP Server