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 regular- 64# expression map where patterns are given as regular expres- 65# sions. In this case, the lookups are done in a slightly 66# different way as described below under "REGULAR EXPRESSION 67# 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, delivery 95# diagnostics are directed to that address, instead of to 96# the originator of the message. This is typically used to 97# direct delivery errors to the maintainer of a mailing 98# list, who is in a better position to deal with mailing 99# list delivery problems than the originator of the undeliv- 100# ered mail. 101# 102# The value contains one or more of the following: 103# 104# address 105# Mail is forwarded to address, which is compatible 106# with the RFC 822 standard. 107# 108# /file/name 109# Mail is appended to /file/name. See local(8) for 110# details of delivery to file. Delivery is not lim- 111# ited to regular files. For example, to dispose of 112# unwanted mail, deflect it to /dev/null. 113# 114# |command 115# Mail is piped into command. Commands that contain 116# special characters, such as whitespace, should be 117# enclosed between double quotes. See local(8) for 118# details of delivery to command. 119# 120# When the command fails, a limited amount of command 121# output is mailed back to the sender. The file 122# /usr/include/sysexits.h defines the expected exit 123# status codes. For example, use "|exit 67" to simu- 124# late a "user unknown" error, and "|exit 0" to 125# implement an expensive black hole. 126# 127# :include:/file/name 128# Mail is sent to the destinations listed in the 129# named file. Lines in :include: files have the same 130# syntax as the right-hand side of alias entries. 131# 132# A destination can be any destination that is 133# described in this manual page. However, delivery to 134# "|command" and /file/name is disallowed by default. 135# To enable, edit the allow_mail_to_commands and 136# allow_mail_to_files configuration parameters. 137# 138# ADDRESS EXTENSION 139# When alias database search fails, and the recipient local- 140# part contains the optional recipient delimiter (e.g., 141# user+foo), the search is repeated for the unextended 142# address (e.g., user). 143# 144# The propagate_unmatched_extensions parameter controls 145# whether an unmatched address extension (+foo) is propa- 146# gated to the result of table lookup. 147# 148# CASE FOLDING 149# The local(8) delivery agent always folds the search string 150# to lowercase before database lookup. 151# 152# REGULAR EXPRESSION TABLES 153# This section describes how the table lookups change when 154# the table is given in the form of regular expressions. For 155# a description of regular expression lookup table syntax, 156# see regexp_table(5) or pcre_table(5). NOTE: these formats 157# do not use ":" at the end of a pattern. 158# 159# Each regular expression is applied to the entire search 160# string. Thus, a search string user+foo is not broken up 161# into user and foo. 162# 163# Regular expressions are applied in the order as specified 164# in the table, until a regular expression is found that 165# matches the search string. 166# 167# Lookup results are the same as with indexed file lookups. 168# For security reasons there is no support for $1, $2 etc. 169# substring interpolation. 170# 171# SECURITY 172# The local(8) delivery agent disallows regular expression 173# substitution of $1 etc. in alias_maps, because that would 174# open a security hole. 175# 176# The local(8) delivery agent will silently ignore requests 177# to use the proxymap(8) server within alias_maps. Instead 178# it will open the table directly. Before Postfix version 179# 2.2, the local(8) delivery agent will terminate with a 180# fatal error. 181# 182# CONFIGURATION PARAMETERS 183# The following main.cf parameters are especially relevant. 184# The text below provides only a parameter summary. See 185# postconf(5) for more details including examples. 186# 187# alias_database 188# List of alias databases that are updated by the 189# newaliases(1) command. 190# 191# alias_maps 192# List of alias databases queried by the local(8) 193# delivery agent. 194# 195# allow_mail_to_commands 196# Restrict the usage of mail delivery to external 197# command. 198# 199# allow_mail_to_files 200# Restrict the usage of mail delivery to external 201# file. 202# 203# expand_owner_alias 204# When delivering to an alias that has an owner- com- 205# panion alias, set the envelope sender address to 206# the right-hand side of the owner alias, instead 207# using of the left-hand side address. 208# 209# propagate_unmatched_extensions 210# A list of address rewriting or forwarding mecha- 211# nisms that propagate an address extension from the 212# original address to the result. Specify zero or 213# more of canonical, virtual, alias, forward, 214# include, or generic. 215# 216# owner_request_special 217# Give special treatment to owner-listname and list- 218# name-request addresses. 219# 220# recipient_delimiter 221# Delimiter that separates recipients from address 222# extensions. 223# 224# Available in Postfix version 2.3 and later: 225# 226# frozen_delivered_to 227# Update the local(8) delivery agent's Delivered-To: 228# address (see prepend_delivered_header) only once, 229# at the start of a delivery; do not update the 230# Delivered-To: address while expanding aliases or 231# .forward files. 232# 233# STANDARDS 234# RFC 822 (ARPA Internet Text Messages) 235# 236# SEE ALSO 237# local(8), local delivery agent 238# newaliases(1), create/update alias database 239# postalias(1), create/update alias database 240# postconf(5), configuration parameters 241# 242# README FILES 243# Use "postconf readme_directory" or "postconf html_direc- 244# tory" to locate this information. 245# DATABASE_README, Postfix lookup table overview 246# 247# LICENSE 248# The Secure Mailer license must be distributed with this 249# software. 250# 251# AUTHOR(S) 252# Wietse Venema 253# IBM T.J. Watson Research 254# P.O. Box 704 255# Yorktown Heights, NY 10598, USA 256# 257# ALIASES(5) 258