info > ALIASES

ALIASES(5) File Formats Manual ALIASES(5)

📛 NAME

aliases - Postfix local alias database format

🚀 Quick Reference

Use CaseCommandDescription
Rebuild alias databasenewaliasesRebuild the indexed alias file after editing the text file
Create alias database from text filepostalias /etc/aliasesConvert text aliases file to indexed dbm/db format
Forward mail to addressuser: user@example.comRedirect mail for a local user to an external address
Append mail to fileuser: /var/mail/backupDeliver mail to a file (e.g., for archiving)
Pipe mail to commanduser: "|/usr/bin/procmail"Process incoming mail through a command
Include list from filelist: :include:/path/to/listSend mail to all addresses listed in a file
Owner alias for error handlingowner-list: admin@example.comDirect delivery errors to the list maintainer

📋 SYNOPSIS

newaliases

📝 DESCRIPTION

The aliases(5) table provides a system-wide mechanism to redirect mail for local recipients. The redirections are processed by the Postfix local(8) delivery agent.

Normally, the aliases(5) table is specified as a text file that serves as input to the postalias(1) command. The result, an indexed file in dbm or db format, is used for fast lookup by the mail system. Execute the command newaliases in order to rebuild the indexed file after changing the Postfix alias database.

When the table is provided via other means such as NIS, LDAP or SQL, the same lookups are done as for ordinary indexed files.

Alternatively, the table can be provided as a regular-expression map where patterns are given as regular expressions. In this case, the lookups are done in a slightly different way as described below under "REGULAR EXPRESSION TABLES".

Users can control delivery of their own mail by setting up .forward files in their home directory. Lines in per-user .forward files have the same syntax as the right-hand side of aliases(5) entries.

The format of the alias database input file is as follows:

The name is a local address (no domain part). Use double quotes when the name contains any special characters such as whitespace, #, :, or @. The name is folded to lowercase, in order to make database lookups case insensitive.

In addition, when an alias exists for owner-name, this will override the envelope sender address, so that delivery diagnostics are directed to owner-name, instead of the originator of the message (for details, see owner_request_special, expand_owner_alias and reset_owner_alias). This is typically used to direct delivery errors to the maintainer of a mailing list, who is in a better position to deal with mailing list delivery problems than the originator of the undelivered mail.

The value contains one or more of the following:

📬 ADDRESS EXTENSION

When alias database search fails, and the recipient localpart contains the optional recipient delimiter (e.g., user+foo), the search is repeated for the unextended address (e.g., user).

The propagate_unmatched_extensions parameter controls whether an unmatched address extension (+foo) is propagated to the result of table lookup.

🔤 CASE FOLDING

The local(8) delivery agent always folds the search string to lowercase before database lookup.

🔍 REGULAR EXPRESSION TABLES

This section describes how the table lookups change when the table is given in the form of regular expressions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5). NOTE: these formats do not use ":" at the end of a pattern.

Each regular expression is applied to the entire search string. Thus, a search string user+foo is not broken up into user and foo.

Regular expressions are applied in the order as specified in the table, until a regular expression is found that matches the search string.

Lookup results are the same as with indexed file lookups. For security reasons there is no support for $1, $2 etc. substring interpolation.

🔒 SECURITY

The local(8) delivery agent disallows regular expression substitution of $1 etc. in alias_maps, because that would open a security hole.

The local(8) delivery agent will silently ignore requests to use the proxymap(8) server within alias_maps. Instead it will open the table directly. Before Postfix version 2.2, the local(8) delivery agent will terminate with a fatal error.

⚙️ CONFIGURATION PARAMETERS

The following main.cf parameters are especially relevant. The text below provides only a parameter summary. See postconf(5) for more details including examples.

📜 STANDARDS

RFC 822 (ARPA Internet Text Messages)

👀 SEE ALSO

📚 README FILES

Use "postconf readme_directory" or "postconf html_directory" to locate this information.

DATABASE_README, Postfix lookup table overview

📄 LICENSE

The Secure Mailer license must be distributed with this software.

👤 AUTHOR(S)

Wietse Venema
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA

Wietse Venema
Google, Inc.
111 8th Avenue
New York, NY 10011, USA

ALIASES(5)

ALIASES
📛 NAME 🚀 Quick Reference 📋 SYNOPSIS 📝 DESCRIPTION
📬 ADDRESS EXTENSION 🔤 CASE FOLDING 🔍 REGULAR EXPRESSION TABLES 🔒 SECURITY ⚙️ CONFIGURATION PARAMETERS 📜 STANDARDS
👀 SEE ALSO 📚 README FILES 📄 LICENSE 👤 AUTHOR(S)

Generated by phpman v4.9.26-5-g7740029 Author: Che Dong Under GNU General Public License
2026-08-14 21:22 @2600:1f28:365:80b0:4d23:66fa:c2bb:7bae
CrawledBy CCBot/2.0 (https://commoncrawl.org/faq/)
Valid XHTML 1.0 Transitional!Valid CSS!