Content-type: text/html Man page of mail_manual_setup

mail_manual_setup

Section: Environments, Tables, and Troff Macros (7)
Index Return to Main Contents
 

NAME

mail_manual_setup - Describes how to manually set up and start mail  

DESCRIPTION

Manually setting up and starting your Tru64 UNIX mail system involves stopping and starting the sendmail utility, making changes to the /var/adm/sendmail/sendmail.cf and /var/adm/sendmail/hostname.m4 files, and running the newaliases command. This reference page also provides information about the four mail utilities included in the Tru64 UNIX operating system, and the sendmail utility.  

Setting Up Your Mail System

Setting up your mail delivery system requires that you understand how the sendmail utility works and how to modify the /var/adm/sendmail/sendmail.cf file and the m4 files.  

The sendmail Utility

The sendmail utility is a general-purpose mail router that enables a user to send mail to users on the same and other systems. In most cases, the mail utilities rely on sendmail to parse mail addresses and to resolve system aliases. Specifically, when a message is sent, the message goes through the following delivery process: The mail utility passes the message to the sendmail utility. The sendmail utility checks its aliases database for full expansion of system names. The sendmail utility parses the address of the receiver of the mail according to a set of rules. If the message is going to a user on the same system as the sender, sendmail passes the message to the mail utility for delivery. If the message is going to a user on a remote system, sendmail forwards the message to the sendmail utility (or the equivalent utility for systems other than Tru64 UNIX) on the remote system by using one of the following protocols, as specified in the address: DECnet
Used to send mail with DECnet (for example, host::user). uux
Used to send mail with the UNIX-to-UNIX Copy Program (UUCP) (for example, decosf!user). SMTP
Used to send mail with the Transmission Control Protocol/Internet Protocol (TCP/IP) facility (for example, [email protected]). Once the message arrives on the correct system, the sendmail (or equivalent) utility passes the message to the mail utility for delivery to the receiver's mailbox.
 

The sendmail Configuration File

The sendmail configuration file, sendmail.cf, contains the instructions for how your mail is sent and delivered, and how it is parsed. This file includes several tunable macros that you can modify to suit your environment, and one macro that you should be aware of but cannot modify. For more information, see the sendmail(8) reference page.  

Using m4 Files

Alternatively, you can use the mailconfig GUI or mailsetup script to fine tune your mail configuration. For more information, see the mailconfig(8X) and the mailsetup(8) reference pages and the Network Administration manual.

You can edit the /var/admin/sendmail/hostname.m4 file, modifying the define lines. The file contains comment lines (lines that begin with dnl), that provide additional information. For example, the following define line specifies that RFC976-style addressing is disabled: define (_RFC976, {})dnl To enable RFC976-style addressing, modify the line as follows: define (_RFC976, {T})dnl The T enables RFC976-style addressing. After you edit the file, change to the /var/adm/sendmail directory and issue the following command:

# make -f Makefile.cf.hostname: This command generates a hostname.cf file. To use the new configuration, copy the hostname.cf file to sendmail.cf and restart sendmail by using the /sbin/init.d/sendmail restart command.

For more information, see the m4(1) and sendmail.m4(8) reference pages.  

User Configurable Mail Locking

Different mailers use different methods to lock mailbox files. Tru64 UNIX enables you to configure the locking style. To do this, use the /usr/sbin/rcmgr set command to set MAILLOCKING in the /etc/rc.config file.

Valid values for MAILLOCKING are as follows: Specifies lockf. Specifies lockfile. Specifies Multi-channel Memo Distribution Facility (MMDF). This applies to MH only. Specifies lockf. Specifies that both lockf and lockfile are used.  

Restrictions

Spool files are locked while being modified by using the lockf call and by using a lock file (/var/spool/mail/$USER.lock). When spool files are NFS-mounted the NFS lockd daemon should be running on both the client and server machine. Any user-added program that modifies the spool area must use lockf, the lock file method of locking, or both.

ULTRIX Version 4.3 and earlier versions use lock file locking. Queue files (which reside in the /var/spool/mqueue directory) are locked using lockf. Sharing mqueue over NFS is supported with NFS locking (lockd) enabled.  

Starting the Mail System

To start the mail system, use the following procedure: Edit the /var/adm/sendmail/sendmail.cf file to change the macro definitions described in the Network Administration. Issue the newaliases command to initialize the sendmail aliases database as follows:

# newaliases Stop the current sendmail process by using the following command:

# /sbin/init.d/sendmail stop Start the sendmail utility as follows:

# /sbin/init.d/sendmail start

SMTP Mail Service started Alternatively, steps 2 through 4 can be accomplished by using the restart option to the sendmail startup script as follows:

# /sbin/init.d/sendmail restart This command does the following: Initializes the sendmail aliases database Stops the current sendmail process Starts the sendmail utility  

Setting Up the Post Office Protocol

The Post Office Protocol (POP) offers users an alternative to the standard mail system. To enable users on your system to use POP for mail, you must enable the mh POP server (popd). To set up a POP server, log in as super user and perform the following steps: Create a group called pop in /etc/group. For more information on adding groups, see addgroup(8). Add pop and all POP users to /etc/group. For example: pop:*:99:pop,pop-user1,pop-user2,pop-user3 In this example, 99 is the groupd ID and pop-user1 pop-user2 pop-user3 are the POP users that are being added. Create an account called pop in /etc/passwd, with /var/spool/pop as the home directory. For example: pop:*:199:99:POP Account:/var/spool/pop:/: In this example, 199 is the user ID. For more information, see adduser(8). Create a directory called /var/spool/pop and make pop the owner by entering the following commands:

# mkdir /var/spool/pop # chown pop /var/spool/pop Change the group ID of /usr/spool/pop to pop by entering the following command:

# chgrp pop /var/spool/pop Change the owner of /usr/lib/mh/spop to pop by entering the following command:

# chown pop /usr/lib/mh/spop

Check the permissions on the file to be certain they are set to rwsr-xr-x. Create a file named /usr/spool/pop/POP and add an entry to the file in the following format for every user who will be served by the POP server: user::user:::user@<client_address>::::0 See pop(4) for more information. Change the owner of /usr/spool/pop/POP to pop by entering the following command:

# chown pop /usr/spool/pop/POP

Check the permissions on the file to be certain they are set to -rw-r--r--. Run the popaka program to obtain an alias for every user entered in the /usr/spool/pop/POP database. See the popaka reference page for more information. Edit the system wide aliases file (/var/adm/sendmail/aliases) to include the strings produced from running the popaka program. Run the newaliases program to update the system wide aliases database. Run the popwrd program to enter a password for each POP server user. See popwrd(8) for more information. Run the popd server in the background and redirect the output to a null file. For example:

# /usr/lib/mh/popd >/dev/null 2>&1 & The Tru64 UNIX popd sever is based on the pop3 protocol. By default, it uses port 109. If the popd application is using port 110, you can do start the popd sever with the -p option to indicate the port number. Alternatively, you can change the port number by editing the /etc/services file.

If you are running in a Network Information Service (NIS) environment, perform the following steps to enable users on client machines to reply to or send mail so that the return address is correctly sent to the POP server machine: Ensure that NIS aliases for the POP user point to the POP server machine. Run mailsetup and select the quick option or modify the send mail configuration file to specify the POP server machine. Check the svc.conf to ensure the local, yp aliases exist. If not, add them.

If you need to start the popd daemon from a script run from the /sbin/rc3.d directory as part of the system reboot process, you should start it using the following command: /usr/lib/mh/popd >/dev/null 2>&1 & You can start the script after the network is started, but before the script for the window manager is started.  

RELATED INFORMATION

Commands: mail(1), mailx(1), popaka(8), popd(8), popwrd(8), rc0(8), mailconfig(8X).

Files: aliases(4), pop(4), sendmail.cf(4).

Network: mail_intro(7).

System calls: syslog(3).

Network Administration delim off


 

Index

NAME
DESCRIPTION
Setting Up Your Mail System
The sendmail Utility
The sendmail Configuration File
Using m4 Files
User Configurable Mail Locking
Restrictions
Starting the Mail System
Setting Up the Post Office Protocol
RELATED INFORMATION

This document was created by man2html, using the manual pages.
Time: 02:40:19 GMT, October 02, 2010