The alias database exists in two forms.
One is a text form,
maintained in the file
/etc/aliases. The aliases are of the form
Only local names may be aliased;
- name: name1, name2, ...
will not have the desired effect
(except on prep.ai.MIT.EDU,
and they probably don't want me).
Aliases may be continued by starting any continuation lines
with a space or a tab.
Blank lines and lines beginning with a sharp sign
#) are comments.
- email@example.com.MIT.EDU: eric@CS.Berkeley.EDU
The second form is processed by the
This form is in the files
/etc/aliases.pag. This is the form that
sendmail actually uses to resolve aliases.
This technique is used to improve performance.
The control of search order is actually set by the service switch.
Essentially, the entry
is always added as the first alias entry;
also, the first alias file name without a class
nis: on the front)
will be used as the name of the file for a ``files'' entry
in the aliases switch.
For example, if the configuration file contains
and the service switch contains
then aliases will first be searched in the NIS database,
then in /etc/aliases,
then in the NIS+ database.
- aliases nis files nisplus
You can also use
For example, the specification:
will first search the /etc/aliases file
and then the map named
my.nis.domain. Warning: if you build your own
be sure to provide the
-l flag to
makedbm(8) to map upper case letters in the keys to lower case;
otherwise, aliases with upper case letters in their names
won't match incoming addresses.
Additional flags can be added after the colon
exactly like a
K line -- for example:
will search the appropriate NIS map and always include null bytes in the key.
- OAnis:-N firstname.lastname@example.org
[Contents] [Previous] [Next]
Questions or problems regarding this web site should be directed to Steve Gielda.
Copyright © 1999 www.cotse.com. All rights reserved.
Last modified: Friday April 02, 1999.