1# 2# Sample aliases file. Install in the location as specified by the 3# output from the command "postconf alias_maps". Typical path names 4# are /etc/aliases or /etc/mail/aliases. 5# 6# >>>>>>>>>> The program "newaliases" must be run after 7# >> NOTE >> this file is updated for any changes to 8# >>>>>>>>>> show through to Postfix. 9# 10 11# Person who should get root's mail. Don't receive mail as root! 12#root: you 13 14# Basic system aliases -- these MUST be present 15MAILER-DAEMON: postmaster 16postmaster: root 17 18# General redirections for pseudo accounts 19bin: root 20daemon: root 21named: root 22nobody: root 23uucp: root 24www: root 25ftp-bugs: root 26postfix: root 27 28# Put your local aliases here. 29 30# Well-known aliases 31manager: root 32dumper: root 33operator: root 34abuse: postmaster 35 36# trap decode to catch security attacks 37decode: root 38 39# ALIASES(5) ALIASES(5) 40# 41# NAME 42# aliases - Postfix local alias database format 43# 44# SYNOPSIS 45# newaliases 46# 47# DESCRIPTION 48# The aliases(5) table provides a system-wide mechanism to 49# redirect mail for local recipients. The redirections are 50# processed by the Postfix local(8) delivery agent. 51# 52# Normally, the aliases(5) table is specified as a text file 53# that serves as input to the postalias(1) command. The 54# result, an indexed file in dbm or db format, is used for 55# fast lookup by the mail system. Execute the command 56# newaliases in order to rebuild the indexed file after 57# changing the Postfix alias database. 58# 59# When the table is provided via other means such as NIS, 60# LDAP or SQL, the same lookups are done as for ordinary 61# indexed files. 62# 63# Alternatively, the table can be provided as a regu- 64# lar-expression map where patterns are given as regular 65# expressions. In this case, the lookups are done in a 66# slightly different way as described below under "REGULAR 67# EXPRESSION TABLES". 68# 69# Users can control delivery of their own mail by setting up 70# .forward files in their home directory. Lines in per-user 71# .forward files have the same syntax as the right-hand side 72# of aliases(5) entries. 73# 74# The format of the alias database input file is as follows: 75# 76# o An alias definition has the form 77# 78# name: value1, value2, ... 79# 80# o Empty lines and whitespace-only lines are ignored, 81# as are lines whose first non-whitespace character 82# is a `#'. 83# 84# o A logical line starts with non-whitespace text. A 85# line that starts with whitespace continues a logi- 86# cal line. 87# 88# The name is a local address (no domain part). Use double 89# quotes when the name contains any special characters such 90# as whitespace, `#', `:', or `@'. The name is folded to 91# lowercase, in order to make database lookups case insensi- 92# tive. 93# 94# In addition, when an alias exists for owner-name, this 95# will override the envelope sender address, so that deliv- 96# ery diagnostics are directed to owner-name, instead of the 97# originator of the message (for details, see 98# owner_request_special, expand_owner_alias and 99# reset_owner_alias). This is typically used to direct 100# delivery errors to the maintainer of a mailing list, who 101# is in a better position to deal with mailing list delivery 102# problems than the originator of the undelivered mail. 103# 104# The value contains one or more of the following: 105# 106# address 107# Mail is forwarded to address, which is compatible 108# with the RFC 822 standard. 109# 110# /file/name 111# Mail is appended to /file/name. For details on how 112# a file is written see the sections "EXTERNAL FILE 113# DELIVERY" and "DELIVERY RIGHTS" in the local(8) 114# documentation. Delivery is not limited to regular 115# files. For example, to dispose of unwanted mail, 116# deflect it to /dev/null. 117# 118# |command 119# Mail is piped into command. Commands that contain 120# special characters, such as whitespace, should be 121# enclosed between double quotes. For details on how 122# a command is executed see "EXTERNAL COMMAND DELIV- 123# ERY" and "DELIVERY RIGHTS" in the local(8) documen- 124# tation. 125# 126# When the command fails, a limited amount of command 127# output is mailed back to the sender. The file 128# /usr/include/sysexits.h defines the expected exit 129# status codes. For example, use "|exit 67" to simu- 130# late a "user unknown" error, and "|exit 0" to 131# implement an expensive black hole. 132# 133# :include:/file/name 134# Mail is sent to the destinations listed in the 135# named file. Lines in :include: files have the same 136# syntax as the right-hand side of alias entries. 137# 138# A destination can be any destination that is 139# described in this manual page. However, delivery to 140# "|command" and /file/name is disallowed by default. 141# To enable, edit the allow_mail_to_commands and 142# allow_mail_to_files configuration parameters. 143# 144# ADDRESS EXTENSION 145# When alias database search fails, and the recipient local- 146# part contains the optional recipient delimiter (e.g., 147# user+foo), the search is repeated for the unextended 148# address (e.g., user). 149# 150# The propagate_unmatched_extensions parameter controls 151# whether an unmatched address extension (+foo) is propa- 152# gated to the result of table lookup. 153# 154# CASE FOLDING 155# The local(8) delivery agent always folds the search string 156# to lowercase before database lookup. 157# 158# REGULAR EXPRESSION TABLES 159# This section describes how the table lookups change when 160# the table is given in the form of regular expressions. For 161# a description of regular expression lookup table syntax, 162# see regexp_table(5) or pcre_table(5). NOTE: these formats 163# do not use ":" at the end of a pattern. 164# 165# Each regular expression is applied to the entire search 166# string. Thus, a search string user+foo is not broken up 167# into user and foo. 168# 169# Regular expressions are applied in the order as specified 170# in the table, until a regular expression is found that 171# matches the search string. 172# 173# Lookup results are the same as with indexed file lookups. 174# For security reasons there is no support for $1, $2 etc. 175# substring interpolation. 176# 177# SECURITY 178# The local(8) delivery agent disallows regular expression 179# substitution of $1 etc. in alias_maps, because that would 180# open a security hole. 181# 182# The local(8) delivery agent will silently ignore requests 183# to use the proxymap(8) server within alias_maps. Instead 184# it will open the table directly. Before Postfix version 185# 2.2, the local(8) delivery agent will terminate with a 186# fatal error. 187# 188# CONFIGURATION PARAMETERS 189# The following main.cf parameters are especially relevant. 190# The text below provides only a parameter summary. See 191# postconf(5) for more details including examples. 192# 193# alias_database (see 'postconf -d' output) 194# The alias databases for local(8) delivery that are 195# updated with "newaliases" or with "sendmail -bi". 196# 197# alias_maps (see 'postconf -d' output) 198# The alias databases that are used for local(8) 199# delivery. 200# 201# allow_mail_to_commands (alias, forward) 202# Restrict local(8) mail delivery to external com- 203# mands. 204# 205# allow_mail_to_files (alias, forward) 206# Restrict local(8) mail delivery to external files. 207# 208# expand_owner_alias (no) 209# When delivering to an alias "aliasname" that has an 210# "owner-aliasname" companion alias, set the envelope 211# sender address to the expansion of the 212# "owner-aliasname" alias. 213# 214# propagate_unmatched_extensions (canonical, virtual) 215# What address lookup tables copy an address exten- 216# sion from the lookup key to the lookup result. 217# 218# owner_request_special (yes) 219# Enable special treatment for owner-listname entries 220# in the aliases(5) file, and don't split owner-list- 221# name and listname-request address localparts when 222# the recipient_delimiter is set to "-". 223# 224# recipient_delimiter (empty) 225# The set of characters that can separate an email 226# address localpart, user name, or a .forward file 227# name from its extension. 228# 229# Available in Postfix version 2.3 and later: 230# 231# frozen_delivered_to (yes) 232# Update the local(8) delivery agent's idea of the 233# Delivered-To: address (see prepend_deliv- 234# ered_header) only once, at the start of a delivery 235# attempt; do not update the Delivered-To: address 236# while expanding aliases or .forward files. 237# 238# STANDARDS 239# RFC 822 (ARPA Internet Text Messages) 240# 241# SEE ALSO 242# local(8), local delivery agent 243# newaliases(1), create/update alias database 244# postalias(1), create/update alias database 245# postconf(5), configuration parameters 246# 247# README FILES 248# Use "postconf readme_directory" or "postconf html_direc- 249# tory" to locate this information. 250# DATABASE_README, Postfix lookup table overview 251# 252# LICENSE 253# The Secure Mailer license must be distributed with this 254# software. 255# 256# AUTHOR(S) 257# Wietse Venema 258# IBM T.J. Watson Research 259# P.O. Box 704 260# Yorktown Heights, NY 10598, USA 261# 262# Wietse Venema 263# Google, Inc. 264# 111 8th Avenue 265# New York, NY 10011, USA 266# 267# ALIASES(5) 268