Home > Articles > Networking

This chapter is from the book

Aliases

An alias is an alternative name. For electronic mail, you can use aliases to assign additional names to a user, to route mail to a particular system, to define mailing lists, to send e-mail through programs for processing, and to append e-mail messages to a file for later use.

You can create a mail alias for each user at your site to specify where the mail is stored. Providing a mail alias is like providing a mail stop as part of the address for an individual at a large corporation. If you do not provide the mail stop, the mail is delivered to a central address. Extra effort is required to determine where the mail is to be delivered within the building, and the possibility of error increases. For example, if two people named Kevin Smith work in the same building, the probability is high that each Kevin will receive mail intended for the other.

Use domains and location-independent addresses as much as possible when you create alias files. To enhance the portability and flexibility of alias files, make your alias entries as generic and system independent as possible. For ex_ample, if you have a user named ignatz on system oak in domain Eng.sun.com, create the alias as ignatz instead of ignatz@Eng or ignatz@oak. If the user ignatz changes the name of the system but remains within the engineering domain, you do not need to update any alias files to reflect the change in the system name.

When creating aliases that include users outside your domain, create the alias with the user name and the domain name. For example, if you have a user named smallberries on system privet in domain Corp.sun.com, create the alias as smallberries@Corp.

NOTE

You can set an option in the *.mc file that generates the sendmail.cf file to translate the e-mail address to a fully qualified domain namea domain name that contains all of the elements needed to specify where an electronic mail message should be delivered or where an NIS+ table is located—when mail goes outside the user's domain. See Chapter 2, "Customizing sendmail Configuration Files" for more information.

Figure 4 shows how sendmail uses aliases. Programs that read mail, such as /usr/bin/mailx, can have aliases of their own, which are expanded before the message reaches sendmail.

Figure 4 How sendmail Uses Aliases

As system administrator, you should choose a policy for updating aliases and forwarding mail messages. You might set up an aliases mailbox as a place for users to send requests for mail forwarding and changes to their default mail alias. If your system uses NIS or NIS+, you can administer forwarding instead of forcing users to manage it themselves. A common mistake users make is to put a .forward file in the home directory of Host A that forwards mail to user@host-b. When the mail gets to Host B, sendmail looks up the user in the NIS or NIS+ aliases and sends the message back to user@host-a, resulting in a loop and more bounced mail.

Uses for Alias Files

You create mail aliases for global use in the NIS+ aliases table, in the NIS aliases map, or, if your site does not use a nameservice, in local /etc/mail/aliases files. You can also create and administer mailing lists with the same alias files.

Depending on the configuration of your mail services, you can administer aliases with the NIS or NIS+ nameservice to maintain a global aliases database or by updating all of the local /etc/mail/aliases files to keep them in sync. See Chapter 4, "Setting Up and Administering Mail Services" for information on how to create aliases.

In general, only the mail hub for an e-mail domain contains the full list of aliases. The client systems and gateways have no idea how to deliver e-mail to individuals. They forward or relay e-mail to the mail hub for handling. Unless you have multiple mail hubs, you don't need to put aliases into NIS or NIS+.

Creating User Aliases

Users can also create and use aliases. They can create aliases either in their local .mailrc file, which only they can use, or in their system's local /etc/mail/aliases file, which anyone can use. Users cannot create or administer NIS or NIS+ alias files. Users cannot administer the local /etc/mail/aliases file unless they have access to the root password on their system.

Including Files in Aliases

You can keep an alias list in a separate file and include a reference to it in the aliases file with the following syntax.

mailinglistname: :include:pathname

The following example includes an alias named engineers that is located in the /etc/mail/includes/engineers file.

engineers: :include:/etc/mail/includes/engineers

If you want to delegate the administration of aliases to others, use the chown command to change the ownership of the included file to the name of the user. Then, with the following syntax, create an alias that designates the owner of the alias.

owner-mailinglistname: username

mailinglistname is the name of the mailing list and username is the login name of the person responsible for administering the alias. The following example assigns ownership of the alias named engineers to user winsor.

owner-engineers: winsor

Individuals can then use the owner-engineers alias to send e-mail to the person responsible for administering the alias.

Sending Mail to Files and Programs

You also can have aliases send e-mail to files and programs.

The following example appends all e-mail sent to listings-log to /proj/dev/logs/listings-log.

listings-log: /proj/dev/logs/listings-log

The following example sends all e-mail sent to weblogs as standard input to the program /usr/local/bin/analyze-web-logs.

weblogs: "/usr/local/bin/analyze-web-logs"

For program aliases, the program must provide an appropriate exit status that is returned to sendmail; otherwise sendmail bouces all e-mails sent to this kind of aliases. sendmail is very picky about these return values. The appropriate values are listed in /usr/include/sysexits.h.

Syntax of Aliases

The following sections describe the syntax of NIS+, NIS, and .mailrc aliases.

NIS+ Aliases

The NIS+ aliases table contains all of the names by which a system or person is known, except for private aliases listed in users' local .mailrc files. The sendmail program can use the NIS+ Aliases database instead of the local /etc/mail/aliases files to determine mailing addresses. See the aliasadm(8) and nsswitch.conf(4) manual pages for more information.

The NIS+ aliases table has the following format.

alias: expansion [options#  "comments"]

The NIS+ aliases table columns, are described in Table 6.

Table 6 Columns in the NIS+ Aliases Database

Column

Description

alias

The name of the alias.

expansion

The value of the alias as it would appear in a sendmail /etc/aliases file.

options

Reserved for future use.

comments

Use to add specific comments about an individual alias.


The NIS+ Aliases database should contain entries for all mail clients. You list, create, modify, and delete entries in the NIS+ Aliases database with the aliasadm command. If you are creating a new NIS+ aliases table, you must initialize the table before you create the entries. If the table already exists, no initialization is needed.

When creating alias entries, enter one alias per line. You should have only one entry that contains the user's system name. For example, you could create the following entries for a user named winsor on system castle.

winsor: janice.winsor
jwinsor: janice.winsor
janicew: janice.winsor
janice.winsor: winsor@castle

You can create an alias for local names or domains. For example, an alias entry for the user fred, who has a mailbox on the system oak and is in the domain Trees, could have the following entry in the NIS+ aliases table.

fred: fred@Trees

To use the aliasadm command, you must be root, a member of the NIS+ group that owns the Aliases database, or the person who created the database.

See Chapter 4, "Setting Up and Administering Mail Services" for information on how to create NIS+ alias tables.

NIS Aliases

Aliases in the NIS aliases map have the following format.

name: name1, name2, . . .

.mailrc Aliases

Aliases in a .mailrc file have the following format.

alias aliasname name1 name2 name3 . . .

/etc/mail/aliases Aliases

Distribution list formats in a local /etc/mail/aliases file have the following format.

aliasname: name1,name2,name3 . . .

The aliases in the /etc/mail/aliases file are stored in text form. When you edit the /etc/mail/aliases file, run the newaliases program to create a DBM database to make the aliases available to the sendmail program in binary form.

The Solaris 8 release provides the new /usr/bin/praliases command that you can use to display the contents of the /etc/mail/aliases file as key:value pairs. If you specify an argument on the command line, the command displays any matching key:value pair.

The following example uses the praliases command to display all of the aliases on the system paperbark.

paperbark% praliases
mailer-daemon:postmaster
postmaster:root
winsor:winsor@paperbark
nobody:/dev/null
ignatz:ignatz@paperbark
@:@
paperbark%

The following example uses the praliases command with a username argument to display the alias for user ignatz.

paperbark% praliases ignatz
ignatz:ignatz@paperbark
paperbark%

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020