New Built-in Mailer Feature
The old [TCP] built-in mailer is not available.
Use the P=[IPC] built-in mailer instead. The interprocess
communications ([IPC]) built-in mailer now enables delivery
to a UNIX domain socket on systems that support it. You can use this mailer
with LMTP delivery agents that listen on a named socket.
An example mailer might resemble the following.
Mexecmail, P=[IPC], F=lsDFMmnqSXzA5@/:|, E=\r\n,
S=10, R=20/40, T=DNS/RFC822/X-Unix, A=FILE /var/run/lmtpd
|
The first mailer argument in the [IPC] mailer is
now checked for a legitimate value. The following table provides possible
values for the first mailer argument.
Table 24-20 Possible Values for the First Mailer Argument
Value | Description |
A=FILE | Use for UNIX domain socket delivery |
A=TCP | Use
for TCP/IP connections |
A=IPC | Is no
longer available as a first mailer argument |
New Rule Sets
The following table lists the new rule sets and describes what the rule
sets do.
Table 24-21 New Rule Sets
Set | Description |
check_eoh | Correlates information that is gathered between headers and checks for missing
headers. This rule set is used with the macro storage map and is called after
all of the headers have been collected. |
check_etrn | Uses the ETRN command (as check_rcpt
uses RCPT). |
check_expn | Uses the EXPN command (as check_rcpt
uses RCPT). |
check_vrfy | Uses the VRFY command (as check_rcpt uses RCPT). |
The following list describes new rule set features.
Numbered rule sets are also named, but the rule sets can still
be accessed by their numbers.
The H header configuration file command
allows for a default rule set to be specified for header checks. This rule
set is called only if the individual header has not been assigned its own
rule set.
Comments in rule sets (that is, text within parentheses) are
not removed if the configuration file version is nine or greater. For example,
the following rule matches the input token (1), but does
not match the input token.
sendmail accepts the SMTP RSET command even when it rejects commands because of TCP wrappers or
the check_relay rule set.
You receive a warning if you set the OperatorChars option multiple times. Also, do not set OperatorChars after the rule sets are defined.
The name of the rule set, as well as its lines, are ignored
if an invalid rule set is declared. The rule set lines are not added to S0.
Changes to Files
Note the following changes.
The helpfile is now located in /etc/mail/helpfile. The old name (/etc/mail/sendmail.hf) has a symbolic link that points to the new name.
The trusted-users file is now located
in /etc/mail/trusted-users. During an upgrade, if the
old name (/etc/mail/sendmail.ct) is detected, but not
the new name, a hard link from the old name to the new name is created. Otherwise,
no change is made. The default content is root.
The local-host-names file is now located
in /etc/mail/local-host-names. During an upgrade, if
the old name (/etc/mail/sendmail.cw) is detected, but
not the new name, a hard link from the old name to the new name is created.
Otherwise, no change is made. The default content is zero length.
The new name for /usr/lib/mail/cf/main-v7sun.mc is /usr/lib/mail/cf/main.mc.
The new name for /usr/lib/mail/cf/subsidiary-v7sun.mc is /usr/lib/mail/cf/subsidiary.mc.
IPv6 Addresses in Configuration
In version 8.12 of sendmail, IPv6 addresses that
are used in configuration should be prefixed with the IPv6:
tag to identify the address properly. If you are not identifying an IPv6 address,
a prefix tag is not used.
Changes to mail.local
The following table describes the new command-line options for the mail.local program, which is used by sendmail
as a delivery agent for local mail.
Table 24-22 New Command-Line Options for mail.local
Option | Description |
-7 | Prevents the
Local Mail Transfer Protocol (LMTP) mode from advertising 8BITMIME support
in the LHLO response |
-b | Causes a permanent
error instead of a temporary error if a mailbox exceeds its quota |
mail.local is the default for LMTP mode. However,
for this release, if you choose to use mail.local as the
local delivery agent without being in LMTP mode, you need to do one of the
following to set the S flag.
Use the following syntax for the configuration file.
MODIFY_MAILER_FLAGS(`LOCAL', `+S') # for the configuration file
|
Alternately, perform the following two steps for m4
configuration.
define(`MODIFY_MAILER_FLAGS', `S')dnl # first step
MAILER(local)dnl # second step
|
Note - MODIFY_MAILER_FLAGS is a new macro that is
used to build the configuration file. For details, refer to New Macros Used to Build the sendmail Configuration
File.
For a complete review, refer to the mail.local(1M) man page.
Changes to mailstats
The mailstats program, which provides statistics
on mailer usage, is packaged with the sendmail program.
The following table describes new options in mailstats.
Table 24-23 New mailstats Options
Option | Description |
-C filename | Specifies a sendmail configuration file |
-p | Provides clear
statistics in a program-readable mode |
-P | Also provides clear statistics in a program-readable
mode, but this option does not truncate the statistics file |
For more information, refer to the mailstats(1) man page.
Changes to makemap
The makemap command creates keyed database files
for sendmail. The following table describes new makemap options. When you declare options, use the following syntax.
makemap options class filename
|
When you use the preceding syntax, remember the following. options are preceded by a dash
(for example, -dN).
class refers to the type of database
(for example, btree, dbm, or hash).
filename refers to the full path
(or relative name) for the database file.
Table 24-24 New makemap Options
Option | Description |
-C | Uses the specified sendmail configuration file for finding the TrustedUser option |
-c | Uses the specified hash and btree cache size |
-e | Allows an empty value from the right-hand side (RHS) |
-l | Lists map types that are supported |
-t | Specifies a different delimiter, instead of white
space |
-u | Dumps (unmaps)
the contents of the database to standard output |
Note - If makemap is running as root, the ownership
of the generated maps is automatically changed to the TrustedUser, as specified in the sendmail configuration
file. For more information about the TrustedUser
option, refer to Table 24-2.
For more information, refer to the makemap(1M) man page.
|