HP-UX Mailing Services Administrator’s Guide HP-UX 11i v1 and HP-UX 11i v2 Manufacturing Part Number: 5991-6611 July 2006 © Copyright 2006 Hewlett-Packard Development Company L.P.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
© Copyright 1985-86, 1988 Massachusetts Institute of Technology. © Copyright 1989-93 The Open Software Foundation, Inc. © Copyright 1986 Digital Equipment Corporation. © Copyright 1990 Motorola, Inc. © Copyright 1990, 1991, 1992 Cornell University © Copyright 1989-1991 The University of Maryland © Copyright 1988 Carnegie Mellon University Trademark Notices UNIX is a registered trademark of The Open Group.
Contents About This Document 1. Mailing Services Overview The elm Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How elm Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The elm Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The mailx Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Setting Mail Header Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limiting Message Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeout.* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataFileBufferSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XscriptFileBufferSize . . . . . .
Contents Configuring Sendmail to Reject Unsolicited Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Anti-Spamming Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the gen_cf Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Access Database to Allow or Reject Mail Messages. . . . . . . . . . . . . . . . . . Access Database Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Configuring and Reading the Sendmail Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Setting Log Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Understanding syslog Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Storing Off Old Sendmail Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Printing and Reading the Mail Queue. . . . . .
Contents The submit.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 New Menu Options in the gen_cf Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 The /usr/newconfig/etc/mail/cf/cf/gen_cf Script . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 10
About This Document This manual describes the Mailing Services implemented in the HP-UX 11i v2 operating system.It is one of the five manuals documenting the Internet Services suite of products. See “Related Documentation” on page 13 for a list of the other new Internet Services manuals. These manuals replace the manual Installing and Administering Internet Services (B2355-90685), which was shipped with previous releases of the operating system.
Table 1 HP-UX 11i Releases (Continued) Supported Processor Architecture Release Identifier Release Name B.11.20 HP-UX 11i v1.5 Intel® Itanium® Processor Family B.11.22 HP-UX 11i v1.6 Intel® Itanium® Processor Family B.11.23 HP-UX 11i v2.0 Intel® Itanium® Processor Family PA-RISC Publishing History Table 2 provides, for a particular document, the manufacturing part number, the respective operating systems, and the publication date.
Table 3 describes the content in more detail. Table 3 Document Organization Chapter Description Mailing Services Overview Provides an overview of the Mail User Agents and the Mail Transport Agent implemented in the HP-UX 11i v2 operating system. Configuring and Administering Sendmail Describes the various steps involved in configuring Sendmail.
• HP-UX Internet Services Administrator’s Guide Provides an overview of the Internet Services products and describes how to install and configure them on your HP-UX 11i v2 operating system. You can access this manual at the following URL: http://www.docs.hp.com/hpux/netcom/index.html#Internet%2 0Services • HP-UX Routing Services Administrator’s Guide Provides an overview of the routing daemons, gated and mrouted, supported in the HP-UX 11i v2 operating system.
• Other Documents For detailed technical and conceptual information about BIND, as well as information about planning a BIND hierarchy and using Sendmail with BIND, HP recommends that you read DNS and BIND, by Paul Albitz and Cricket Liu, published by O’Reilly and Associates, Inc. You can get information about the book (including retail outlets where you can buy it, as well as how to order it directly from O’Reilly) by visiting the O’Reilly Website http://www.ora.
HP Encourages Your Feedback HP welcomes any comments and suggestions you have on this manual. You can send your comments in the following ways: • Internet electronic mail: netinfo_feedback@cup.hp.com • Using a feedback form located at the following URL: http://docs.hp.com/assistance/feedback.html Please include the following information along with your comments: 16 • The full title of the manual and the part number. (The part number appears on the title page of printed and PDF versions of a manual.
1 Mailing Services Overview Mailers are a set of UNIX commands that provide command-line interfaces for users to send and receive messages over the network.
Mailing Services Overview (MUA), communicate with a Mail Transport Agent (MTA) to send mail messages to the appropriate destination, and receive messages destined to the end user’s mailbox. An MUA is a program that allows users to compose and read electronic mail messages. The MUA provides an interface between the user and the MTA. An outgoing mail is eventually delivered to an MTA for delivery, and the incoming messages are collected from the MTA.
Mailing Services Overview This chapter discusses the following topics: CAUTION Chapter 1 • elm • mailx • mail/rmail • sendmail Do not use two separate mail programs simultaneously to access the same mail file. This may cause unpredictable results.
Mailing Services Overview The elm Utility The elm Utility The elm utility is based on the public domain elm program. An electronic mail for UNIX, elm is a Mail User Agent (MUA) system designed to run with Sendmail or with any other UNIX MTA configured on your system.
Mailing Services Overview The elm Utility For a detailed description of all the commands used to edit and send mail messages, type man 1M elm at the HP-UX prompt. The elm Configuration File The elm configuration file, $HOME/.elm/elmrc, defines the initial values for the elm configuration variables. You can create the configuration file by choosing the o option (the options menu) in the main menu, which displays a list of all the elm configuration variables.
Mailing Services Overview The mailx Utility The mailx Utility mailx is an interactive message processing system. It provides a flexible environment for sending and receiving messages electronically. mailx provides commands to save, delete, and reply to messages. You can use mailx to edit, review, and modify messages. By default, incoming mail is stored in a standard file called a system mailbox, unless you specify an alternate mailbox file using the -f option.
Mailing Services Overview The mailx Utility Table 1-2 Time Zones Supported by mailx nst ast adt est edt cst cdt mst mdt pst pdt yst ydt hst hdt gmt bst eet eest met mest wet west jst aest aesst acst acsst awst acdt at bt btt Cat cct cest cet ckt clst clt cot cut ect emt fst gst gt hfe ict ist it kdt kst lst mdt mpt msd msk mt mut pmt pnt sst tmt tst ut wst aedt aft ahdt ahst akdt akst amst amt anast anat art azost azst azt b
Mailing Services Overview The mailx Utility Table 1-2 Time Zones Supported by mailx (Continued) sadt sast sbt sct set sgt srt swt tft tha that tjt tkt tot trut tuc tvt ulast ulat usz1 usz1s usz18 usz3 usz3s usz4 usz4s usz5 usz5s usz6 usz6s usz7 usz7s usz8 usz8s usz9 usz9s utc utz uyt uz10 uz11s uz12s uzt vet vlast vlat vtz vut wakt wast wat wesz wez wft wgst wgt wib wita wit wtz wut yakst yakt yapt yekst yekt azot gz NOTE mailx displays
Mailing Services Overview The mail/rmail Utility The mail/rmail Utility You can use mail, the mail user agent to compose and send messages to users. The mail command, when used without arguments, displays all the messages, with the last received message displayed first. For each message, mail prints a ? prompt, and reads a line from the standard input to determine the disposition of the message. mail exits automatically when the last message is displayed.
Mailing Services Overview The Sendmail Utility The Sendmail Utility Sendmail acts as a post office, to which all messages can be submitted for routing. Sendmail interprets both Internet (that is, user@domain) and UUCP (that is, host!user) styles of addressing. The Sendmail configuration file controls how the addresses are interpreted. Sendmail can rewrite message addresses to conform to standards on many common target networks.
Mailing Services Overview The Sendmail Utility • “Default Client/Server Operation” on page 35 • “How Sendmail Handles Errors” on page 36 Message Structure A message has three parts: an envelope, a message header, and a message body. The envelope consists of the sender address, recipient address, and routing information shared by programs that create, route, and deliver the message. It is usually not seen directly by either the sender or the recipients of the message.
Mailing Services Overview The Sendmail Utility 3. Passes the mail to one of the several specialized delivery agents for delivery. Figure 1-1 outlines the flow of messages through Sendmail. After Sendmail collects a message, it routes the message to each of the specified recipient addresses. In order to route a message to a particular address, Sendmail must resolve that address to a {delivery agent, host, user} triple.
Mailing Services Overview The Sendmail Utility Figure 1-1 Flow of Mail Through Sendmail User mail/rmail ... elm mail Sendmail OpenMail Delivery Agent X.400 Delivery Agent SMTP Delivery OpenMail or X.25 Network X.400 Network Local Area Network OpenMail Receiving Agent X.
Mailing Services Overview The Sendmail Utility If an address resolves to the local mailer, Sendmail looks up the address in its alias database and expands it appropriately if it is found. The aliasing facility or a user’s .forward file can be used to route mail to programs and to files. (Sendmail does not mail directly to programs or files.) Mail to programs is normally piped to the prog mailer (/usr/bin/sh -c), which executes the command specified in the alias or .forward file definition.
Mailing Services Overview The Sendmail Utility If your host has a direct UUCP connection to the next host in the path, the mail is delivered to that host through UUCP. If not, the message is returned with an error. The supplied configuration file provides detailed instructions for arranging to relay such mail through hosts to which you can connect.
Mailing Services Overview The Sendmail Utility otherwise inaccessible. For information on creating MX records, see HP-UX IP address and Client Management Guide at the URL http://www.docs.hp.com/hpux/netcom/index.html#Internet%20Se rvices. MX records are used only if a message address resolves to an IPC mailer (that is, one that uses SMTP over sockets to perform delivery).
Mailing Services Overview The Sendmail Utility ;name bling ttl class IN IN IN MX MX MX MX preference 0 20 30 mail exchanger bling.paf.edu. wheo.paf.edu. munch.pag.edu. Normally, mail for bling will go directly to bling. However, if bling is down, or if the sending host cannot connect to bling, Sendmail will route mail for bling to wheo. If wheo is also down or unreachable, Sendmail will route the mail to munch. Naturally, for this to be useful, wheo and munch must be able to route mail to bling.
Mailing Services Overview The Sendmail Utility in temporary failures, but the attempt to connect to munch fails permanently, the message is returned as an error. If the attempts to connect to bling and wheo result in permanent failures, but the attempt to connect to munch fails temporarily, the message is queued. • A host cannot deliver a message to another host for which it is a mail exchanger.
Mailing Services Overview The Sendmail Utility gBJ2va 02544 5 Wed Dec 18 21:57 /var/spool/mqueue/g2 is empty /var/spool/mqueue/g3 is empty Total Requests: 0 root root An efficient queue file-naming system is also being provided in this release. The algorithm used to name files ensures that the names will be unique for 60 years. The queued items can be moved between queues with ease. Default Client/Server Operation This section describes the operation of Sendmail servers and clients.
Mailing Services Overview The Sendmail Utility mailclient. (The Sendmail installation script sets the DH macro value to the host specified by SENDMAIL_SERVER_NAME.) Outgoing mail that is not local is sent by mailclient to the remote host using MX records. Because the DM macro entry in the /etc/mail/sendmail.cf file on mailclient is set to mailserv.company.com, mail from user1 appears to be from user1@mailserv.company.com. Because mail sent to remote hosts from user1 is sent from user1@mailserv.company.
Mailing Services Overview The Sendmail Utility • Temporary failures that have remained in the mail queue for the queue timeout period (set with the Timeout.queuereturn option in the /etc/mail/sendmail.cf file), which is normally five days. • Local recipient user unknown. • The recipient address cannot be resolved by the configuration file. • Permanent delivery agent (mailer) failures. • Inability to find an Internet address for a remote host.
Mailing Services Overview The Sendmail Utility How Sendmail Handles Temporary Failures Messages that fail temporarily are saved in the mail queue and retried later. By default, the mail queue is stored in the directory /var/spool/mqueue. Sendmail saves the message components in two files created in the mail queue directory. The message body is saved in a data file, and the envelope information, the header lines, and the name of the data file are saved in a queue control file.
2 Configuring and Administering Sendmail This chapter describes Sendmail, the Internet Services mail routing utility provided on the HP-UX operating system.
Configuring and Administering Sendmail incoming and outgoing mail messages to the appropriate programs for delivery and further routing. Sendmail allows you to send mail and to receive mail messages from other hosts on a local area network or through a gateway.
Configuring and Administering Sendmail Configuring Sendmail Configuring Sendmail Sendmail is packaged with the core HP-UX 11i v2 operating system. When you install the operating system, Sendmail is automatically installed on your system. The necessary files required for Sendmail operation are created or modified on your system. The Sendmail configuration file supplied with the operating system, sendmail.cf, will work without modifications for most installations.
Configuring and Administering Sendmail Configuring Sendmail The installation script makes the following configuration changes: • Sets the SENDMAIL_SERVER variable in the /etc/rc.config.d/mailservs file to 1. This ensures that the Sendmail daemon is started whenever you reboot your system or run the Sendmail startup script. • Creates /etc/mail/sendmail.cf and /etc/mail/aliases files with default configurations. These files are created with root as the owner and other as the group.
Configuring and Administering Sendmail Configuring Sendmail Configuring Sendmail on a Mail Server This section describes how to configure a system to allow users on other (client) systems to use Sendmail. The mail server receives mail for local users and for the users on client systems. Users on client systems mount the mail directory from the server and read or access mail over an NFS link. For more information on how Sendmail clients and servers work, see “Default Client/Server Operation” on page 35.
Configuring and Administering Sendmail Configuring Sendmail client system) and sends nonlocal mail directly to the destination system or MX host. An outgoing mail message appears to originate from the server, so replies are sent back to the server. For more information on how Sendmail clients and servers work, see “Default Client/Server Operation” on page 35. Sendmail clients can be diskless systems. To configure a Sendmail client system, do the following: 1.
Configuring and Administering Sendmail Configuring Sendmail The client system now forwards local mail to the mail server and forwards other mail directly to remote systems. To configure the client system to relay all mail to the mail server for delivery, see “Modifying the Default Sendmail Configuration File” on page 48. The NFS startup script mounts the /var/mail directory from the mail server to your system.
Configuring and Administering Sendmail Configuring Sendmail Using UUCP Addressing to Send Mail to a Remote User If you are using UUCP addressing, you can verify your Sendmail installation by sending a mail message to a remote user with UUCP transport by using a host!user address, where host is a system to which your local host has a direct UUCP connection. (The uuname command lists the UUCP names of known systems. Type man 1 uuname at the HP-UX prompt for more information.
Configuring and Administering Sendmail Configuring Sendmail Using SMTP Transport to Send Mail to a Remote User If you are using the SMTP Transport, you can verify your Sendmail installation by sending a message to a remote user using a user@host address, where host is a system that provides an SMTP server (for example, the Sendmail daemon). To verify both inbound and outbound SMTP connections, mail the message in a loop, using the syntax user%my_host@remote_host.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File Modifying the Default Sendmail Configuration File The Sendmail configuration file that is supplied with HP-UX works correctly for most Sendmail configurations, so you probably do not need to modify the configuration file. However, certain modifications to the file are supported. This section describes examples of modifications that you may want to make.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File • Specifies how Sendmail must rewrite addresses in the header, if necessary, so that the message address can be understood by the receiving host. The address rewriting process is controlled by sets of address rewriting rules called rulesets. The default configuration file, sendmail.cf, is located in the /usr/newconfig/etc/mail/sendmail.cf directory, and is installed in the /etc/mail/sendmail.cf directory.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File Restarting Sendmail Issue the following commands, on a standalone system or on the mail server, to restart Sendmail: • /sbin/init.d/sendmail stop /sbin/init.d/sendmail start You must restart Sendmail if changes are made to any of the following: • The Sendmail configuration file, /etc/mail/sendmail.cf. • The UUCP configuration, as reflected in the output of the uuname command.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File 2. Set the value of the option MaxHeadersLength=n, where n is the maximum number of lines allowed in the mail header. If a mail header exceeds the maximum value, the following error message is displayed to the sender: 552 Headers too larger #MaxHeadersLength Limiting Message Recipients By default, the maximum number of recipients is 100. You can limit the number of users allowed to receive a single mail message.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File • You can set the frequency of resolver query retransmission using the Timeout.resolver.retrans.normal option. This option sets the Timeout.resolver.retry.first option for the first attempt to deliver a message. It also sets the Timeout.resolver.retry.normal option for all resolver lookups except for the first delivery attempt. The default setting for this option is: #O Timeout.resolver.retry=4 #O Timeout.resolver.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File ProcessTitlePrefix You can specify the prefix string for the process title shown in the ps listings using this option. By default, this option is commented. For example, if you set this option in the sendmail.cf file as: O ProcessTitlePrefix=HPUX_Sendmail-8.11.1 the command ps -ef | grep sendmail | grep -v grep displays sendmail: accepting connections in the output.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File the newly created configuration file. Therefore, HP recommends that you take backup of the configuration file that contains your changes, in case you want to run the gen_cf script again to generate the configuration file again. Relay On This option is equivalent to selecting the following /usr/newconfig/etc/mail/cf/cf/gen_cf script options while generating the /usr/newconfig/etc/mail/cf/cf/sendmail.cf.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File The key can be an IP address, a domain name, a hostname, or an e-mail address. The value part of the database can contain the following values: OK Accepts mail even if other rules in the running ruleset reject it. For example, if the domain name is unresolvable. RELAY Accepts mail addressed to the indicated domain or received from the indicated domain for relaying through your SMTP server.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File You must enable this option only if absolutely necessary because it opens a window for spammers. Specifically, spammers can send mail to your mail server that claims to be from your domain (either directly or through a routed address), and you can then go ahead and relay it out to arbitrary hosts on the Internet.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File Loose relay check This option turns off the default behavior of rechecking all those recipients using the % addressing. For example, if the recipient address is user%site@othersite, the default behavior without the loose_relay_check option is that Sendmail will check if any othersite is an allowed relay host specified in either class R macro or the access db file.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File skipped if a sender has been authenticated using a trusted mechanism, for example, one that is defined via the list of AuthMechanisms. If check_mail returns an error, the RCPT TO command is rejected with that error. If it returns some other result starting with $#, then check_relay is skipped.
Configuring and Administering Sendmail Modifying the Default Sendmail Configuration File Receive only This option generates a sendmail.cf file with a new set of rules called check_compat. You can receive mail messages, but you cannot send them. The following are added in the /etc/rc.config.d/mailservs file: • SENDMAIL_RECVONLY You must set this flag to 1 in order to use the receive_only feature. • SENDMAIL_SENDONLY You must set this flag to 1 in order to use the send_only feature.
Configuring and Administering Sendmail Creating Sendmail Aliases Creating Sendmail Aliases The Sendmail aliases database stores mailing lists and mail aliases. You must create the aliases database by adding aliases to the file /etc/mail/aliases and then by running the /usr/sbin/newaliases command to generate the database from the file. The generated alias database is stored in the file /etc/mail/aliases.db. The Sendmail startup script also generates the aliases database when you reboot your system.
Configuring and Administering Sendmail Creating Sendmail Aliases where alias is the local address, local user name, or local alias, and mailing_list is a comma-separated list of local user names or aliases, remote addresses, file names, commands, or included files. Table 2-1 describes the options that can be included in a mailing list. 3.
Configuring and Administering Sendmail Creating Sendmail Aliases Table 2-1 Mailing List Options (Continued) Option filename Description An absolute pathname on the local machine. Sendmail appends the message to the file if the following conditions are true: • The file exists, is not executable, and is writable by all. • The directory where the file resides is readable and searchable by all. Example: public: /tmp/publicfile terminal: /dev/tty Mail addressed to public is appended to /tmp/publicfile.
Configuring and Administering Sendmail Creating Sendmail Aliases Table 2-1 Mailing List Options (Continued) Option :include:filename Description Any mail addressed to the alias is sent to all the recipients listed in the included file. The file must be a full pathname. Nonroot users can create :include files to maintain their mailing lists. An :include file can contain anything that is specified in the right side of an alias definition.
Configuring and Administering Sendmail Creating Sendmail Aliases chess_club: mike@chem.tech.edu, marie@buffalo, bigvax!amlabs!denise, margaret@hp.com owner-chess_club: mike@chem.tech.edu Any errors that Sendmail encounters while trying to deliver mail to the members of the chess_club mailing list would be reported to mike. Avoiding Alias Loops You must avoid creating aliasing loops. Loops can occur either locally or remotely.
Configuring and Administering Sendmail Creating Sendmail Aliases Creating a Postmaster Alias RFC 2822 requires that a postmaster alias be defined on every host. The postmaster is the person in charge of handling problems with the mail system on that host. The default aliases file supplied with the HP-UX operating system designates the postmaster as root. You can change this alias to the appropriate user for your system.
Configuring and Administering Sendmail Creating Sendmail Aliases The Sendmail program uses the Name Service Switch to determine where to look for Sendmail aliases. Modifying your NIS Aliases Database For information about the NIS or NIS+ aliases database, see Installing and Administering NFS Services, at the URL http://www.docs.hp.com/hpux/onlinedocs/B1031-90048/B1031-90 048.html. Rewriting the From Line on Outgoing Mail HP provides a method that allows the From line on a mail message to be rewritten.
Configuring and Administering Sendmail Creating Sendmail Aliases Forwarding Your Own Mail with a .forward File You can redirect your own mail by creating a .forward file in your home directory. If a .forward file exists in your home directory and is owned by you, Sendmail redirects mail addressed to you to the addresses that the .forward file contains. A .forward file can contain anything that appears on the right side of an alias definition, including programs and files.
Configuring and Administering Sendmail Creating Domain-Specific Aliasing Using Virtual Hosting Creating Domain-Specific Aliasing Using Virtual Hosting Sendmail controls the /etc/mail/virtusertable database. This database provides a domain-specific form of aliasing and also allows multiple domains to be hosted on a single machine. With this feature, users can have their own domain names and receive mail using these domain names with a single host.
Configuring and Administering Sendmail Creating Domain-Specific Aliasing Using Virtual Hosting 3. Create the virtual user table in the /etc/mail directory. A sample virtual user table may look like the following: joe@mydomain.com jane@mydomain.com @mydomain.com jschmoe jdoe@othercompany.com jschmoe In this example, the address joe@mydomain.com is mapped to the local user jschmoe, jane@mydomain.com to the remote user jdoe@othercompany.com, and any other address in mydomain.com is mapped to jschmoe. 4.
Configuring and Administering Sendmail Sendmail and the LDAP Protocol Sendmail and the LDAP Protocol The Lightweight Directory Access Protocol (LDAP) enables servers to share static information. Combining Sendmail and LDAP increases the speed and efficiency at which network information is collected and displayed. Sendmail supports the use of the LDAP protocol to look up addresses. The ldapx class, which is a database, is used to look up items in the LDAP directory service.
Configuring and Administering Sendmail Sendmail and the LDAP Protocol NOTE The LDAP-style options (-v and -h in the previous example) must be double quoted and must follow immediately after the option. Do not leave spaces between the option and the quote. LDAP-Based Routing You can use the LDAP protocol to implement LDAP-based rerouting. This provides a method to reroute addresses with a domain portion in class {LDAPRoute} to either a different mail host or a different address.
Configuring and Administering Sendmail Sendmail and the LDAP Protocol The BindDN parameter used to specify the DN value for the LDAP bind request. For example: -d”cn=ldap://:389,dc=edat104,dc=atl,dc=hp,dc=com” • -h – LDAP servers Space-separated string of servers that support LDAP at your site. For example: -h “ldap1.hp.com ldap2.hp.com” • -p – Port numbers Port numbers where LDAP service is available.
Configuring and Administering Sendmail IPv6 Support IPv6 Support An option value inet6 is provided for the field Family in DaemonPortOptions to enable IPv6 functionality. To enable IPv6, set the DaemonPortOptions in the sendmail.cf configuration file as follows: O DaemonPortOptions=Port=smtp, Name=MTA, Family=inet6 This will enable Sendmail to accept both IPv4 and IPv6 addresses.
Configuring and Administering Sendmail Security Security This section discusses administering Sendmail security options. It discusses the following topics: • “Using the Sendmail Restricted Shell Program” on page 74 • “Turning Off Standard Security Checks” on page 75 • “Enabling SMTP Authentication Based on RFC 2554” on page 77 • “Support for RFC 1413 (Identification Protocol)” on page 79 Using the Sendmail Restricted Shell Program Sendmail allows the aliases file or a user’s .
Configuring and Administering Sendmail Security rmail, and AutoReply are placed in this directory. (You can also specify hard links to the binaries.) Do not place shells such as ksh, sh, csh, and perl in this directory because they have too many security issues. Turning Off Standard Security Checks Sendmail has security checks that limit reading and writing to certain files in a directory.
Configuring and Administering Sendmail Security Table 2-2 Option Values for DontBlameSendmail (Continued) Option Value 76 Description HelpFileinUnsafeDirPath Allow Help file to be in unsafe directory. IncludeFileInGroupWritableDirPath Allows :include: files in group-writable directories. ForwardFileInUnsafeDirPath Allows a .forward file that is in an unsafe directory to include references to programs and files.
Configuring and Administering Sendmail Security Table 2-2 Option Values for DontBlameSendmail (Continued) Option Value Description WriteStatsToHardLink Allows the status file to be a hard link. WritesStatsToSymLink Allows the status file to be a symbolic link. RunProgramInUnsafeDirPath Allows Sendmail to run programs that are in writable directories. RunWritableProgram Allows Sendmail to run programs that are group- or world-writable. WorldWritableAliasFile Accept world-writable alias files.
Configuring and Administering Sendmail Security mainly used for roaming users whose IP address and host name changes repeatedly. In this case, authorization is via a secret password, which is client dependent. The authentication protocol exchange consists of a series of server challenges (otherwise known as a ready response) and client answers that are specific to the authentication mechanism.
Configuring and Administering Sendmail Security Support for RFC 1413 (Identification Protocol) identd is a server that implements the TCP/IP proposed standard IDENT user identification protocol as specified in RFC 1413. identd listens on port 113 and operates by looking up specific TCP/IP connections and returning the user owing the process owning the connection. Sendmail uses identd as an advisory mechanism to log the identity of the user name and host name of the Sendmail client.
Configuring and Administering Sendmail Security Disabling identd from the Sendmail Server This is probably an easier way of disabling identd, because you need not be concerned about the remote client having identd disabled. In the file /etc/mail/sendmail.cf on the Sendmail server, modify the following entry: #O Timeout.ident=5s as O Timeout.ident=0s Now, you need to kill and restart Sendmail.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Configuring Sendmail to Reject Unsolicited Mail You can set up Sendmail so that unsolicited or spam mail (mail sent to large number of users) is not transmitted to or received by users on the network. The first step in configuration is to enable the anti-spamming rulesets. You then edit other configuration files to control mail transmission.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail The access database also allows you to control the message flow. See the section “Using the Access Database to Allow or Reject Mail Messages” on page 82 for more information. Running the gen_cf Script Follow these steps to run the gen_cf script: 1. Log in as root. 2. Go to the directory that contains the script: cd /usr/newconfig/etc/mail/cf/cf/gen_cf 3. Run gen_cf. 4. A list of options is displayed.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail The key can be an IP address, a domain name, a host name or an e-mail address. Table 2-3 Access Database Format Value Description OK Accepts mail even if other rulesets rejects it. For example, if the domain name is unresolvable. RELAY Accepts mail addressed to the specified domain or received from the specified domain for relaying through your SMTP server. RELAY also serves as an implicit OK for the other checks.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Table 2-4 contains a sample access database file, /etc/mail/access. Table 2-4 Access Database Text File Example cyberspammer.com 550 We don’t accept mail from spammers okay.cyberspammer.com OK 128.32 RELAY spammer@aol.com REJECT 192.168.212 DISCARD In the example Access Database text file, all mail messages from the cyberspammer.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Creating the Database Map After creating the Access Database text file, you must use the /usr/sbin/makemap utility to create the database map. Type the following command to create the database: makemap dbm /etc/mail/access < /etc/mail/access The makemap utility takes /etc/mail/access file as input. It then stores the results back into the /etc/mail/access.db file.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Relay Hosts Only: Relaying from Hosts Only By default, host names that are listed as RELAY in both the Access Database and the class R ($=R) macro can relay messages. When using this feature, specify host names. This feature enables Sendmail to look up individual host names and relay messages to the host. See “Checking Headers” on page 88 for information on using the R class.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail • Accept Unqualified Senders • Blacklist Recipients • Realtime Blackhole List Accept Unresolvable Domains This feature enables Sendmail to accept all MAIL FROM: parameters that are not fully qualified, for example, a mail message whose host part of the argument to the MAIL FROM: parameter cannot be located in the host name service, such as DNS.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Mail cannot be sent to spammer@aol.com or to anyone at cyberspammer.com. Realtime Blackhole List This feature rejects hosts listed in the Realtime Blackhole List, which is found in the Realtime Blackhole List server. The server is blackholes.mail-abuse.org. To use this feature, you must add the following line to the DNS database: 1.5.5.192.blackholes.mail-abuse.org IN A 127.0.0.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail the message is discarded. If only one of message recipients address resolves to the $#discard mailer, none of the recipients will receive the mail message. Regular Expressions You can use regular expressions with the new map class regex. Use the regex map to see if an address matches a certain regular expression.
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Spam Control Using the Message Submission Agent (RFC 2476) Sendmail supports RFC 2476, a protocol for message submission. The anti-spam rulesets have been enhanced to improve the anti-spam capabilities. The RFC proposes a new standard for the Message Submission Agent (MSA).
Configuring and Administering Sendmail Configuring Sendmail to Reject Unsolicited Mail Sendmail Validation The check_compat ruleset compares all sender and receiver pairs before mail is delivered. It validates the mail based on the results of the comparison. It checks to see if host A can legally send a message to host B. check_compat is called for all mail deliveries, not just SMTP transactions.
Configuring and Administering Sendmail Turning Off Virtual Interfaces Turning Off Virtual Interfaces You can disable the ability to include all the interface names in the $=w macro on startup. Turning off virtual interfaces speeds up the startup process. However, if you turn virtual interfaces off, mail sent to those addresses will bounce back to the sender. To turn off virtual interfaces, do the following: 1. Open the sendmail.cf file. 2. Uncomment the line DontProbeInterfaces.
Configuring and Administering Sendmail Troubleshooting Sendmail Troubleshooting Sendmail This section describes the following techniques for troubleshooting Sendmail: • “Keeping the Aliases Database Up to Date” on page 93 • “Verifying Address Resolution and Aliasing” on page 94 • “Verifying Message Delivery” on page 94 • “Contacting the Sendmail Daemon to Verify Connectivity” on page 96 • “Setting Your Domain Name” on page 96 • “Attempting to Start Multiple Sendmail Daemons” on page 97 • “Conf
Configuring and Administering Sendmail Troubleshooting Sendmail Verifying Address Resolution and Aliasing In order to deliver a message, Sendmail must first resolve the recipient addresses appropriately. To determine how Sendmail would route mail to a particular address, issue the following command: /usr/sbin/sendmail -bv -v -oL10 address [address...] The -bv (verify mode) option causes Sendmail to verify addresses without collecting or sending a message.
Configuring and Administering Sendmail Troubleshooting Sendmail This is only a test. . Sendmail responds with the following information: myname@baby.com... Connecting to sys1.hp.com via esmtp... 220 sys1.baby.com ESMTP Sendmail 8.8.6 (PHNE_12345)/8.8.6 SMKi t7.02; Wed, 23 Oct 2002 18:44:21 +0530 (IST) 250-sys1.baby.com Hello root@inet.baby.com [15.70.178.1940, pl eased to meet you >>MAIL From: SIZE=21 250 ... Sender ok >> RCPT To: 250
Configuring and Administering Sendmail Troubleshooting Sendmail Contacting the Sendmail Daemon to Verify Connectivity It is possible to contact the Sendmail daemon and other SMTP servers directly with the following command: telnet host 25 Use this to determine whether an SMTP server is running on host. If not, your connection attempt will return the message Connection refused.
Configuring and Administering Sendmail Troubleshooting Sendmail • Modify the /etc/hosts file, making sure that the fully qualified name of the system is listed first. For example, the entry in the file must be 255.255.255.255 dog.hp.com dog and not 255.255.255.255 dog dog.hp.com.
Configuring and Administering Sendmail Troubleshooting Sendmail considered useful. Log levels above 11 are normally used only for debugging purposes. We recommend that you configure syslogd to log mail messages with a priority level of debug and higher. Sendmail’s behavior at each log level is described in Table 2-5. Table 2-5 98 Sendmail Logging Levels Logging Level Behavior 0 No logging. 1 Major problems only. 2 Message collections and failed deliveries. 3 Successful deliveries.
Configuring and Administering Sendmail Troubleshooting Sendmail Table 2-5 Sendmail Logging Levels (Continued) 14-98 Debugging information. This information must be interpreted by your HP service representative. Understanding syslog Entries Sendmail logs the following: • Failures beyond its control (SYSERR). • Administrative activities (for example, rebuilding the aliases database, and killing and restarting the daemon). • Events associated with mail transactions.
Configuring and Administering Sendmail Troubleshooting Sendmail Other details logged in the syslog file are time delay in delivering the message (delay=), type of mailer used (mailer=), priority of the message, relay machine, and the status of the message. Queued messages and SYSERRs are also logged. Storing Off Old Sendmail Log Files At typical logging levels, every piece of mail passing through Sendmail adds two or three lines to the mail log.
Configuring and Administering Sendmail Troubleshooting Sendmail h3TA9Bb29701 86 Wed Feb 9 07:08 janet ess@vetmed.umd.edu ebs@surv.ob.com h3TAATe29713 1482 Tue Feb 15 7:05 carole bja@edp.cloq.potlatch.com vls@ee.cmu.edu h3TABWB29731 10169 Tue Feb 15 8:10 chuck hrm@per.stmarys.com sys6!sysloc@njm The first entry is a message with queue ID h3TA9Bb29701 and a size of 86 bytes. The message arrived in the queue on Wednesday, February 9, at 7:08 a.m. The sender was janet.
Configuring and Administering Sendmail Troubleshooting Sendmail r – Denotes a random number XXXXX – Denotes a 5-digit number that is the process ID of the process creating the queue entry. A file whose name begins with df is a data file. The message body, excluding the header, is kept in this file. A file whose name begins with qf is a queue-control file, which contains the information necessary to process the job. A file whose name begins with xf is a transcript file.
Configuring and Administering Sendmail Troubleshooting Sendmail Table 2-6 Lines in Queue-Control Files (Continued) Initial Letter Content of Line M A message. This line is printed by the mailq command and is generally used to store status information (that is, the reason the message was queued). It can contain any text. R A recipient address. Normally this has already been completely aliased, but it is actually re-aliased when the queue is processed. There is one line for each recipient.
Configuring and Administering Sendmail Troubleshooting Sendmail • The queue option allows multiple -qI, -qR, or -qS queue run limiters. For example, using Sendmail -qRfoo -qRbar will deliver mail to recipients with foo or bar in their address. • The map flag -Tx appends x to lookups that return temporary failure. This is similar to -ax flag, which appends x to lookups that return success. • The QueueSortOrder option is case sensitive.
Configuring and Administering Sendmail Troubleshooting Sendmail M msgsfr bytes_from msgsto 0 0 0K 46 3 41 43K 5 49 51K bytes_to msgsrej msgsdis Mailer 47K 0 0 prog 56 57K 0 0 local 34 34K 0 0 esmtp ============================================================= T 90 C 90 94K 136 138K 136 0 0 0 How to Resolve the Warning Messages To resolve these warning messages, run the following command: # chmod 600 /etc/mail/sendmail.
Configuring and Administering Sendmail Troubleshooting Sendmail How to Resolve Warning Messages When You Send Mail Warning messages may appear when you send mail as a root user. Following is an example statement: #echo “Subject: Testing” | /usr/sbin/sendmail root warning: /etc/mail/aliases has world read or write permission. This is unsafe. warning: /etc/mail/aliases.db has world read or write permission. This is unsafe. warning: /etc/mail/sendmail.st has group read/write or world read/write permission.
3 Sendmail 8.13.3 This chapter discusses the new features in Sendmail 8.13.3, which is the latest Web upgrade of Sendmail available on the HP-UX 11i v1 and HP-UX 11i v2 operating systems.
Sendmail 8.13.3 This chapter discusses the following topics: NOTE 108 • “Overview” on page 109 • “New Features in Sendmail 8.13.3” on page 110 All occurrences to Sendmail in this chapter refer to Sendmail 8.13.3 unless specified explicitly.
Sendmail 8.13.3 Overview Overview Sendmail 8.13.3 is the latest version of Web upgrade available on the HP-UX 11i v1 and HP-UX 11i v2 operating systems at http://www.software.hp.com. The main difference between Sendmail 8.11.1 and Sendmail 8.13.3 is that Sendmail 8.13.3 can act as a Mail Submission Program (MSP) using a different configuration file compared to the one used by the Sendmail daemon MTA. The /etc/mail/submit.cf file is the default Sendmail MSP configuration file.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 New Features in Sendmail 8.13.3 This chapter discusses the following new features in Sendmail 8.13.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 DN Any matches for this attribute are expected to have a value of a fully qualified distinguished name. Sendmail looks up that DN and applies the attributes requested to the returned DN record. FILTER Any matches for this attribute are expected to have a value of an LDAP search filter. Sendmail performs a lookup with the same parameters as the original search but replaces the search filter with the one specified here.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 • Any value in a sendmailMTAAliasValue attribute is added to the result string regardless of the object class. • The mail attribute is added to the result string if the LDAP record is a member of the inetOrgPerson object class. • The uniqueMember attribute is a recursive attribute, used only in groupOfUniqueNames records, and must contain an LDAP DN pointing to another LDAP record. The intention here is to return the mail attribute from those DNs.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 where, hostname specifies the canonical name to which the host will fallback. Mail message forwarded to that host name fails if hostname is an empty string or is the name of a nonexistent host. You can also use macros to represent the hostname. Sendmail expands these macros before connecting to the remote host. If the hostname that you specify for the FallBackSmartHost option exists in the $=w class, Sendmail silently ignores the hostname.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 NOTFOUND Specifies that the key is not found and the result is empty. TEMP Specifies that a temporary failure has occurred. TIMEOUT Specifies that a timeout has occurred on the server side. PERM Specifies that a permanent failure has occurred. In case of an error, that is, when the status is TEMP, TIMEOUT, or PERM, the result field contains an explanatory error message.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 The first two forms describe an IPv4 or IPv6 socket listening on a certain port at a given host or IP address. The last form describes a named socket on the file system at the given path. Following is an example of a socket map that specifies a remote endpoint: KmySocketMap socket inet:12345@127.0.0.1 If multiple socket maps define the same remote endpoint, they share a single connection to this endpoint.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 Table 3-1 Supported DNS Queries (Continued) -R Value Description NS Returns a name server record (RFC 1035) PTR Returns the host name that corresponds to an IP record (RFC 1035) SRV Returns the port to use for a service (RFC 2782) TXT Returns general (human-readable) information (RFC 1035) To make the dns database-map more useful, you can also use the switches described in Table 3-2.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 Support for Deliver By SMTP Extension (RFC 2852) The Delivery By SMTP extension is a mechanism by which an SMTP client can request a server to deliver the message within a prescribed period of time, while transmitting a message to an SMTP server. A client that makes such a request also specifies message handling which must occur if the message cannot be delivered within the specified time period.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 The following sections discuss the anti-spamming features in detail. Message Quarantining Starting with Sendmail 8.13.3, you can quarantine mail messages, which are otherwise known as envelopes. Queue files or envelopes are stored but not considered for delivery or display unless the “quarantine” state of the envelope is undone, or delivery or display of the quarantined items is requested.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 A new error code for the $#error $@ quarantine $: reason, can be used to quarantine message in check_* (except check_compat) and header check rulesets. The $: of the mailer triplet will be used for the quarantine reason. Support for Mail Filter (MILTER) APIs Beginning with Sendmail 8.13.3, you can use the Mail Filter (Milter) APIs to filter all inbound messages through an external filter program.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 The enhancement consists of additional arguments, that is, one or more literal addresses you expect returned when an address must be rejected. Compared to the dnsbl option, you can specify additional arguments (upto 5) to specify the return values from lookups. Sendmail ignores temporary lookup failures in the absence of a third argument, which must be either t or a full error message. By default, any successful lookup generates an error.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 Table 3-3 Q Configuration Command Equates (Continued) Equate Overrides Command-Line Switch/Option Description Interval= (I=) -qInterval Specifies interval between queue runs. Jobs=(J=) MaxQueueRunSize Specifies the maximum number of envelopes per queue run. Nice=(N=) NiceQueueRun Specifies how to renice(3) the queue run. Path=(P=) QueueDirectory Specifies the queue directory or directories.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 For example, the following commands declare a queue directory (the Patch= and P=), and a queue processing interval of 10 minutes (the Interval= and I=): Qslowmail, Path=/disk1/mail/slowqueues, Interval=10m Qslowmail, P=/disk1/mail/slowqueues, I=10m Using queuegroups Through the access Database You must use the gen_cf main menu option to utilize the queuegroup feature to easily select queue groups based on recipient addresses or recipient domains.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 Performance Features Sendmail 8.13.3 contains the following performance enhancement features: • “The FastSplit Option” on page 123 • “SMTP Pipelining” on page 124 • “Connection Caching” on page 124 The following sections discuss the Sendmail 8.13.3 performance features in detail.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 SMTP Pipelining This feature is an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. Using a single TCP send operation for multiple commands improves SMTP performance. SMTP pipelining is an implementation of RFC 1854 (SMTP Service Extension for Command Pipelining).
Sendmail 8.13.3 New Features in Sendmail 8.13.3 A Mail Submission Program (MSP) is another instance of Sendmail that is used for initial mail submission. MSP uses the /etc/mail/submit.cf file as the configuration file. Sendmail 8.13.3 acts as an MSA or MTA depending on the operational mode. The default configuration starting with Sendmail 8.13.3 uses one sendmail binary which acts differently based on the operation mode and supplied options.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 Support for Secured Mail Transaction using STARTTLS STARTTLS is the SMTP command to "Start Transport Layer Security”; or in other words to turn on Secure Socket Layer (SSL). Transport Layer Security (TLS) provides authentication (identification), privacy, confidentiality, and integrity for securing a mail transaction. TLS uses different STARTTLS algorithms for encryption, signing, and message authentication.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 SERVER_KEY and CLIENT_KEY Specifies the private keys that correspond to the certificates of the Sendmail server. Following is the option in the sendmail.cf file: # O # O Server private key ServerKeyFile=/etc/mail/certs/oldreq.pem Client private key ClientKeyFile=/etc/mail/certs/oldreq.pem You can use the /usr/newconfig/etc/mail/cf/cf/gen_cf script to generate the sendmail.cf configuration file that supports the STARTTLS feature.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 The PLAIN Mechanism and sasl_checkpass() Call The PLAIN mechanism is not a secure method of authentication by itself. It is intended for connections that are being encrypted by another level. For example, the IMAP command "STARTTLS" creates an encrypted connection over which PLAIN can be used.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 submit.cf.gen file in the /usr/newconfig/etc/mail/cf/cf/ directory. You must copy the /usr/newconfig/etc/mail/cf/cf/submit.cf.gen file to the /etc/mail directory as submit.cf. New Menu Options in the gen_cf Script Sendmail 8.13.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 You can select the relevant option to display the submenu options. The following discusses the main menu options in detail: • The “General Features” main menu option contains the following submenu options: 1. Delay checks 2. No default MSA 3. LDAP Routing 4. Mailertable 5. Genericstable 6. Domaintable 7. Virtusertable 8. Send only 9. Receive only 10. Queue Groups 11. Accept unresolvable domains 12.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 You can select the relevant submenu option to set the appropriate relay options in the /usr/newconfig/etc/mail/cf/cf/sendmail.cf.gen file. • The “Anti Spamming Options” main menu option contains the following submenu options: 1. Access DB 2. Blacklist Recipients 3. RBL 4. DNSBL 5. Enhanced DNSBL 6.
Sendmail 8.13.3 New Features in Sendmail 8.13.3 NOTE 132 • The “Verify permissions for the sendmail files” menu option verifies the permission of the Sendmail files. In Sendmail 8.11.1, you could use the gen_cf command-line option -v to verify the permissions. Starting with Sendmail 8.13.3, you can also use the gen_cf script to verify the permissions of the Sendmail files. • The “Correct permissions for the sendmail files” menu option corrects the permissions of the Sendmail files.
Index Symbols $HOME/mailrc, 22 *.m4 files, 49 .forward file, 30, 60 /etc/fstab, 44 /etc/mail/aliases, 42 /etc/mail/aliases.*, 60 /etc/mail/aliases.db, 42 /etc/mail/sendmail, 60 /etc/mail/sendmail.cf, 48 /etc/mail/sendmail.cw, 42 /etc/mail/sendmail.st, 60 /etc/mail/virtusertable, 68 /etc/rc.config.d/mailservs, 35, 42, 58 , 59 /etc/rc.config.d/nfsconf, 44 /etc/rc.config.d/nfsconf file, 43 /sbin/init.d/sendmail start, 42 /sbin/init.
Index see mailservs file, 42 /etc/rc.config.
Index resolving the warning message, 105 NFS link, 43 NFS server, 43 NFS Services with sendmail, 45 NFS_CLIENT, 44 NFS_CLIENT variable, 44 NFS_SERVER, 43 NFS_SERVER variable, 43 nfsconf file, 43, 44 NIS with sendmail aliases, 65, 93 NIS+, 43 nispopulate script, 65 no_default_msa, 57 O O’Reilly and Associates, 26 O’Reilly Website, 26 P Permanent failures, 36 error handling, 36 PidFile, 52 postmaster alias, 65 Postmaster Copy, 37 ProcessTitlePrefix, 53 Q QueueDirectory, 34 R receive_only, 59 relay entire doma
Index startup script, 42 troubleshooting, 93 UUCP mailing, 46 validating senders, 86 validation, 91 verbose mode, 94 verifying installation, 45 Sendmail daemon, 42 sendmail logging, 97 sendmail.cf file forwarding non-domain mail, 50 HP-supported changes, 48 sendmail.cf.gen, 49 sendmail.
