mailsetup(8) System Manager's Manual mailsetup(8)
mailsetup - Configures the host's mail system
/usr/sbin/mailsetup [-f file]
Specifies the name of the resulting configuration file.
The mailsetup script sets up the sendmail system on your host. You can use this script to do a quick setup where defaults are used or to do
a more extensive setup. Alternatively, you can use the mailconfig command.
Before you run the mailsetup script, your machine should be established on a local area network (LAN). If you want to use domain-based
addressing, you must also configure the Berkeley Internet Name Domain (BIND) service in your environment. Furthermore, if you want to dis-
tribute your /var/adm/sendmail/aliases database (see aliases(4)) amongst the machines in your environment, you must configure the Network
Information Service (NIS). See the Network Administration guide, bind_intro(7), and nis_intro(7) for more information about the BIND and
For a quick setup, the only information you are asked for is the name of the mail relay you are using and which users are considered local.
For the more extensive setup, you are asked for the same information in addition to UUCP, DECnet, and UMC configuration information, mail
aliases for your machine, local address formats, and other domain information.
You must run the mailsetup script as superuser and with the system in multiuser mode.
When you run mailsetup a menu is displayed giving you a choice of responses. You are then prompted for further information.
If you do not use the -f option, before mailsetup exits, it asks if you wish to restart your mail with this new configuration. If you
answer no, your configuration file is saved in /var/adm/sendmail/sendmail.cf.tmp and the install is aborted. If you answer yes, your
/var/adm/sendmail/sendmail.cf file is moved to /var/adm/sendmail/sendmail.cf.orig, if no file by this name exists. If /var/adm/send-
mail/sendmail.cf.orig exists, /var/adm/sendmail/sendmail.cf is moved to /var/adm/sendmail/sendmail.cf.n, where n is the version number (0
to 6 where 0 is the most recent). The new configuration file is then moved to /var/adm/sendmail/sendmail.cf and sendmail is restarted.
If you use the -f option, the configuration file is saved with the file name specified and sendmail is not restarted.
The mailsetup script produces the following three files in /var/adm/sendmail: sendmail.m4 hostname.m4 Makefile.cf.hostname
You can fine tune your configuration by modifying the hostname.m4 file and issuing a make -f Makefile.cf.hostname command, which produces a
hostname.cf file. You can then copy the hostname.cf file to sendmail.cf and restart sendmail using the /sbin/init.d/sendmail restart com-
To set up your mail system using the mailsetup script, log in as root and complete the following steps: Invoke the mailsetup script. The
script asks whether you want to do a quick setup. If you answer yes, the mailsetup script prompts you for the following information: The
name of the general-purpose relay If you want to modify the list of aliases and users that are considered local If you want to complete the
To do an advanced mail setup, answer no. The mailsetup script prompts you for the information you collected on the worksheet. When
you finish providing the information, the mailsetup script asks if you want to complete the configuration. If you answer yes, the
script moves the new sendmail.cf file to the system space, saves the old sendmail.cf file, and restarts sendmail. If you answer no,
the script moves the new sendmail.cf file to /var/adm/sendmail/sendmail.cf.tmp and exits.
Running mailsetup in a TruCluster Server Cluster
The following restrictions apply to setting up mail with the mailsetup script in a TruCluster Server cluster: You can run the mailsetup
script on an entire cluster, but not focused on any one cluster member. If you try to run mailsetup with the -focus option, you will see
the following error message: Mail can only be configured for the entire cluster. The cluster members and the cluster alias are added to
the Cw macro, which defines the nicknames for the cluster. If you delete the cluster members or the cluster alias from the nicknames list
via the mailsetup script, they are added again.
If you do a quick setup with the mailsetup script, the cluster members and the cluster alias are automically added to the Cw macro
(nicknames list) and you are not prompted to update the list of nicknames. Any file that includes the hostname string as part of
the file name is changed to includecluster_alias. For example, hostname.m4 becomes cluster_alias.m4 and Makefile.cf.hostname becomes
Contains alias definitions for the sendmail program. Specifies the users who should receive mail on the local host. Specifies the send-
mail configuration file. Specifies the mail setup product description for the configuration file. Specifies the backup configuration
files. Specifies the original configuration file. Specifies the configuration file produced by mailsetup. Specifies the user config-
urable file produced by mailsetup. In a TruCluster Server cluster, this file is named after the cluster alias, i.e., cluster_alias.m4.
Specifies the Makefile file produced by mailsetup and used to make a hostname.cf file from the sendmail.cf and hostname.m4 files. In a Tru-
Cluster Server cluster, this file is named after the cluster alias, i.e., Makefile.cf.cluster_alias.
Commands: m4(1), , mailconfig(8), sendmail(8)
Introductions: mail_intro(7), bind_intro(7), nis_intro(7)