Part I Network Services Topics
Part II Accessing Network File Systems Topics
4. Managing Network File Systems (Overview)
5. Network File System Administration (Tasks)
6. Accessing Network File Systems (Reference)
8. Planning and Enabling SLP (Tasks)
10. Incorporating Legacy Services
Local Mail and a Remote Connection
Setting Up Mail Services (Task Map)
Changing the sendmail Configuration (Task Map)
Changing the sendmail Configuration
How to Build a New sendmail.cf File
How to Automatically Rebuild a Configuration File
How to Use sendmail in the Open Mode
How to Manage Mail Delivery by Using an Alternate Configuration of sendmail.cf
Administering Mail Alias Files (Task Map)
Administering Mail Alias Files
How to Initiate an NIS+ mail_aliases Table
How to List the Contents of the NIS+ mail_aliases Table
How to Add Aliases to the NIS+ mail_aliases Table From the Command Line
How to Add Entries by Editing an NIS+ mail_aliases Table
How to Edit Entries in an NIS+ mail_aliases Table
How to Set Up an NIS mail.aliases Map
How to Set Up a Local Mail Alias File
How to Create a Keyed Map File
How to Create a postmaster Alias in Each Local /etc/mail/aliases File
How to Create a Separate Mailbox for postmaster
How to Add the postmaster Mailbox to the Aliases in the /etc/mail/aliases File
Administering the Queue Directories (Task Map)
Administering the Queue Directories
How to Display the Contents of the Mail Queue, /var/spool/mqueue
How to Force Mail Queue Processing in the Mail Queue, /var/spool/mqueue
How to Run a Subset of the Mail Queue, /var/spool/mqueue
How to Move the Mail Queue, /var/spool/mqueue
How to Run the Old Mail Queue, /var/spool/omqueue
Administering .forward Files (Task Map)
How to Change the .forward-File Search Path
How to Create and Populate /etc/shells
Troubleshooting Procedures and Tips for Mail Services (Task Map)
Troubleshooting Procedures and Tips for Mail Services
How to Test the Mail Configuration
How to Test the sendmail Rule Sets
How to Verify Connections to Other Systems
Other Sources for Mail Diagnostic Information
Part V Serial Networking Topics
15. Solaris PPP 4.0 (Overview)
16. Planning for the PPP Link (Tasks)
17. Setting Up a Dial-up PPP Link (Tasks)
18. Setting Up a Leased-Line PPP Link (Tasks)
19. Setting Up PPP Authentication (Tasks)
20. Setting Up a PPPoE Tunnel (Tasks)
21. Fixing Common PPP Problems (Tasks)
22. Solaris PPP 4.0 (Reference)
23. Migrating From Asynchronous Solaris PPP to Solaris PPP 4.0 (Tasks)
25. Administering UUCP (Tasks)
Part VI Working With Remote Systems Topics
27. Working With Remote Systems (Overview)
28. Administering the FTP Server (Tasks)
29. Accessing Remote Systems (Tasks)
Part VII Monitoring Network Services Topics
Mail aliases must be unique within the domain. This section provides the procedures for administering mail alias files. Alternately, you can use the Mailing List feature in the Solaris Management Console to perform these tasks on the aliases database.
In addition, you can create database files for the local mail host by using makemap. Refer to the makemap(1M) man page. The use of these database files does not provide all of the advantages of using a name service such as NIS or NIS+. However, you should be able to retrieve the data from these local database files faster because no network lookups are involved. For more information, refer to Interactions of sendmail With Name Services and Mail Alias Files in Chapter 14, Mail Services (Reference).
Choose from the following procedures:
You can use the aliasadm command to manage entries in an NIS+ table. To create a table, follow these instructions. For more information, refer to the aliasadm(1M) man page.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# aliasadm -I
To add two or three aliases, refer to How to Add Aliases to the NIS+ mail_aliases Table From the Command Line.
To add more than two or three aliases, refer to How to Add Entries by Editing an NIS+ mail_aliases Table.
To see a complete list of the contents of the table, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# aliasadm -1
For more information, refer to the aliasadm(1M) man page.
Example 13-3 Listing an Individual Entry From the NIS+ mail_aliases Table
Alternately, you can use the aliasadm command to list individual entries. After you complete the first step in this procedure, type the following:
# aliasadm -m ignatz ignatz: ignatz@saturn # Alias for Iggy Ignatz
The command matches only the complete alias name, not partial strings. You cannot use metacharacters, such as * and ?, with aliasadm -m.
Example 13-4 Listing Partial Matches From the NIS+ mail_aliases Table
Also, you can use the aliasadm command to list partial matches. After you complete the first step in this procedure, type the following:
# aliasadm -l | grep partial-string
Replace partial-string with the desired string for your search.
To add two or three aliases to the table, follow the following instructions. If you are adding more than two or three aliases, see How to Add Entries by Editing an NIS+ mail_aliases Table.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
If you are creating a completely new NIS+ mail_aliases table, you must first initiate the table. To complete this task, refer to How to Initiate an NIS+ mail_aliases Table.
See this example of a typical entry.
# aliasadm -a iggy iggy.ignatz@saturn "Iggy Ignatz"
The following list describes the input from the preceding example.
The option for adding an alias
The short form of the alias name
The expanded alias name
The name for the alias in quotation marks
# aliasadm -m alias
The entry that you created
For more information, refer to the aliasadm(1M) man page.
You can use the aliasadm command to manage entries in an NIS+ table. To add more than two or three aliases to the table, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# aliasadm -e
This command displays the table and enables you to edit the table. The editor that you use has been set with the $EDITOR environment variable. If this variable is not set, vi is the default editor.
alias: expanded-alias # ["option" # "comments"]
This column is for the short form of the alias name.
This column is for the expanded alias name.
This column is reserved for future use.
This column is used for comments about the individual alias, such as a name for the alias.
If you leave the option column blank, type an empty pair of quotation marks ("") and add the comments.
The order of the entries is not important to the NIS+ mail_aliases table. The aliasadm -l command sorts the list and displays the entries in alphabetical order.
For more information, refer to Mail Alias Files and the aliasadm(1M) man page.
To edit entries in the table, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# aliasadm -m alias
Replace alias with the assigned alias name.
# aliasadm -c alias expanded-alias [options comments]
If necessary, edit the alias name.
If necessary, edit the expanded alias name.
If necessary, edit the option.
If necessary, edit the comment for this entry.
For more information, refer to the aliasadm(1M) man page, as well as Mail Alias Files.
# aliasadm -m alias
For more information, refer to the aliasadm(1M) man page.
Example 13-5 Deleting Entries From an NIS+ mail_aliases Table
To delete entries from the table, use the following syntax after you complete the first step in this procedure:
# aliasadm -d alias
Replace alias with the alias name for the entry that you are deleting.
Use the following procedure to facilitate aliasing with an NIS mail.aliases map.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# cat /etc/mail/aliases .. alias:expanded-alias
Use the short alias name.
Use the expanded alias name (user@host.domain.com).
# cat /etc/mail/aliases .. Postmaster: root
# cat /etc/mail/aliases .. root: user@host.domain.com
Use the assigned address of the designated postmaster.
# cd /var/yp
# make
The changes in the /etc/hosts and /etc/mail/aliases files are propagated to NIS slave systems. The changes are active in only a few minutes, at most.
Use the following procedure to resolve aliases with a local mail alias file.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
user1: user2@host.domain
Use the new alias name.
Use the actual address for the new alias.
# cat /etc/mail/aliases .. Postmaster: root
# cat /etc/mail/aliases .. root: user@host.domain.com
Use the assigned address of the designated postmaster.
# newaliases
The configuration of the AliasFile option in /etc/mail/sendmail.cf determines whether this command generates in binary form either the single file, /etc/mail/aliases.db, or the pair of files, /etc/mail/aliases.dir and /etc/mail/aliases.pag.
You can copy the three files by using the rcp or rdist commands. Refer to the rcp(1) man page or the rdist(1) man page for more information. Alternately, you can create a script for this purpose.
When you copy these files, you do not need to run the newaliases command on each of the other systems. However, remember that you must update all the /etc/mail/aliases files each time you add or remove a mail client.
You can copy these files by using the rcp or rdist commands. Refer to the rcp(1) man page or the rdist(1) man page for more information. Alternately, you can create a script for this purpose.
When you copy these files, you do not need to run the newaliases command on each of the other systems. However, remember that you must update all the /etc/mail/aliases files each time you add or remove a mail client.
To create a keyed map file, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
Entries can have the following syntax.
old-name@newdomain.com new-name@newdomain.com old-name@olddomain.com error:nouser No such user here @olddomain.com %1@newdomain.com
Use the user name that was previously assigned with the domain that is newly assigned.
Use the address that is newly assigned.
Use the user name that was previously assigned with the domain that was previously assigned.
Use the domain that was previously assigned.
Use the domain that is newly assigned.
The first entry redirects mail to a new alias. The next entry creates a message when an incorrect alias is used. The last entry redirects all incoming mail from olddomain to newdomain.
# /usr/sbin/makemap maptype newmap < newmap
Select a database type, such as dbm, btree, or hash.
Use the name of the input file and the first part of the name of the database file. If the dbm database type is selected, then the database files are created by using a .pag and a .dir suffix. For the other two database types, the file name is followed by .db.
Every system must be able to send mail to a postmaster mailbox. You can create an NIS or NIS+ alias for postmaster, or you can create the alias in each local /etc/mail/aliases file. Refer to these procedures.
How to Create a postmaster Alias in Each Local /etc/mail/aliases File
How to Add the postmaster Mailbox to the Aliases in the /etc/mail/aliases File
If you are creating the postmaster alias in each local /etc/mail/aliases file, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# cat /etc/mail/aliases # Following alias is required by the mail protocol, RFC 2821 # Set it to the address of a HUMAN who deals with this system's # mail problems. Postmaster: root
Change root to the mail address of the person who is designated as the postmaster.
Postmaster: mail-address
Use the assigned address for the person who is designated as the postmaster.
You can create a separate mailbox for the postmaster to keep postmaster mail separate from personal mail. If you create a separate mailbox, use the mailbox address instead of the postmaster's personal mail address when you edit the /etc/mail/aliases files. For details, refer to How to Create a Separate Mailbox for postmaster.
If you are creating a separate mailbox for postmaster, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
For details about adding a user account, refer to Chapter 5, Managing User Accounts and Groups (Tasks), in System Administration Guide: Basic Administration.
# mail -f postmaster
Use the assigned address.
If you are adding a postmaster mailbox to the aliases in the /etc/mail/aliases file, follow these instructions.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# cat /etc/mail/aliases .. root: user@host.domain.com
Use the assigned address of the person who is designated as postmaster.
# cat /etc/mail/aliases .. sysadmin: /usr/somewhere/somefile
Create a name for a new alias.
Use the path to the local mailbox.
# newaliases