Skip Navigation Links | |
Exit Print View | |
Managing sendmail Services in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
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 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
Mail aliases must be unique within the domain. This section provides the procedures for administering mail alias files.
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. 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 3, Mail Services (Reference).
Use the following procedure to facilitate aliasing with an NIS mail.aliases map.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: 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.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: 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 rsync commands. Refer to the rcp(1) man page or the rsync(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 rsync commands. Refer to the rcp(1) man page or the rsync(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.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: 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 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.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: 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.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.
For details about adding a user account, refer to Setting Up and Managing User Accounts by Using the CLI (Task Map) in Managing User Accounts and User Environments in Oracle Solaris 11.1.
# 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.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: 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