Technical data

Configuring and Managing SMTP
17.5 Modifying the SMTP Configuration
• TCPIP$SMTP_MIME_HACK
When set, SMTP accepts 8BITMIME requests from SMTP clients, preventing
the clients from converting the message into a 7-bit format. For more
information, see Section 17.9.2.
17.6 Configuring SMTP AntiSPAM
SPAM is the Internet equivalent of junk mail and is a growing source of
annoyance to Internet users. TCP/IP Services SMTP contains antiSPAM, which
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.
17.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
(see Section 17.5).
The SMTP.CONFIG file should be owned by TCPIP$SMTP and protection should
be set to (W:RE).
SMTP.CONFIG is an ASCII text file consisting of one or more lines formatted as
follows:
Field1: Value1
Field2: Value2
.
.
.
In this format:
• Field names start in column 1, are terminated with a colon (:), and are not
case sensitive.
• Values vary depending on the field. Limitations and restrictions are described
in Table 17–4.
If a value consists of a list of items, specify them on multiple lines by
pressing the Tab key before continuing the value on the subsequent lines. For
example:
Field1: Item1,
Tab
Item2,
Tab
Item3
Field2: Value2
Or specify each value as a separate instance of same field. For example:
Field1: Item1
Field1: Item2
Field1: Item3
An alternative format is:
Field1: Item1, Item2, Item3
Configuring and Managing SMTP 17–15