summaryrefslogtreecommitdiffhomepage
path: root/postfix/aliases
diff options
context:
space:
mode:
Diffstat (limited to 'postfix/aliases')
-rw-r--r--postfix/aliases268
1 files changed, 268 insertions, 0 deletions
diff --git a/postfix/aliases b/postfix/aliases
new file mode 100644
index 0000000..04a104f
--- /dev/null
+++ b/postfix/aliases
@@ -0,0 +1,268 @@
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#
10pham: pham
11
12# Person who should get root's mail. Don't receive mail as root!
13root: pham
14
15# Basic system aliases -- these MUST be present
16MAILER-DAEMON: postmaster
17postmaster: pham
18
19# General redirections for pseudo accounts
20bin: pham
21daemon: pham
22named: pham
23nobody: pham
24uucp: pham
25www: pham
26ftp-bugs: pham
27postfix: pham
28
29# Put your local aliases here.
30
31# Well-known aliases
32manager: pham
33dumper: pham
34operator: pham
35abuse: postmaster
36
37# trap decode to catch security attacks
38decode: pham
39
40# custom
41devnull: /dev/null
42
43# ALIASES(5) ALIASES(5)
44#
45# NAME
46# aliases - Postfix local alias database format
47#
48# SYNOPSIS
49# newaliases
50#
51# DESCRIPTION
52# The aliases(5) table provides a system-wide mechanism to
53# redirect mail for local recipients. The redirections are
54# processed by the Postfix local(8) delivery agent.
55#
56# Normally, the aliases(5) table is specified as a text file
57# that serves as input to the postalias(1) command. The
58# result, an indexed file in dbm or db format, is used for
59# fast lookup by the mail system. Execute the command
60# newaliases in order to rebuild the indexed file after
61# changing the Postfix alias database.
62#
63# When the table is provided via other means such as NIS,
64# LDAP or SQL, the same lookups are done as for ordinary
65# indexed files.
66#
67# Alternatively, the table can be provided as a regu-
68# lar-expression map where patterns are given as regular
69# expressions. In this case, the lookups are done in a
70# slightly different way as described below under "REGULAR
71# EXPRESSION TABLES".
72#
73# Users can control delivery of their own mail by setting up
74# .forward files in their home directory. Lines in per-user
75# .forward files have the same syntax as the right-hand side
76# of aliases(5) entries.
77#
78# The format of the alias database input file is as follows:
79#
80# o An alias definition has the form
81#
82# name: value1, value2, ...
83#
84# o Empty lines and whitespace-only lines are ignored,
85# as are lines whose first non-whitespace character
86# is a `#'.
87#
88# o A logical line starts with non-whitespace text. A
89# line that starts with whitespace continues a logi-
90# cal line.
91#
92# The name is a local address (no domain part). Use double
93# quotes when the name contains any special characters such
94# as whitespace, `#', `:', or `@'. The name is folded to
95# lowercase, in order to make database lookups case insensi-
96# tive.
97#
98# In addition, when an alias exists for owner-name, this
99# will override the envelope sender address, so that deliv-
100# ery diagnostics are directed to owner-name, instead of the
101# originator of the message (for details, see
102# owner_request_special, expand_owner_alias and
103# reset_owner_alias). This is typically used to direct
104# delivery errors to the maintainer of a mailing list, who
105# is in a better position to deal with mailing list delivery
106# problems than the originator of the undelivered mail.
107#
108# The value contains one or more of the following:
109#
110# address
111# Mail is forwarded to address, which is compatible
112# with the RFC 822 standard.
113#
114# /file/name
115# Mail is appended to /file/name. See local(8) for
116# details of delivery to file. Delivery is not lim-
117# ited to regular files. For example, to dispose of
118# unwanted mail, deflect it to /dev/null.
119#
120# |command
121# Mail is piped into command. Commands that contain
122# special characters, such as whitespace, should be
123# enclosed between double quotes. See local(8) for
124# details of delivery to command.
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 a user name
226# from its extension (example: user+foo), or a .for-
227# ward file name from its extension (example: .for-
228# ward+foo).
229#
230# Available in Postfix version 2.3 and later:
231#
232# frozen_delivered_to (yes)
233# Update the local(8) delivery agent's idea of the
234# Delivered-To: address (see prepend_deliv-
235# ered_header) only once, at the start of a delivery
236# attempt; do not update the Delivered-To: address
237# while expanding aliases or .forward files.
238#
239# STANDARDS
240# RFC 822 (ARPA Internet Text Messages)
241#
242# SEE ALSO
243# local(8), local delivery agent
244# newaliases(1), create/update alias database
245# postalias(1), create/update alias database
246# postconf(5), configuration parameters
247#
248# README FILES
249# Use "postconf readme_directory" or "postconf html_direc-
250# tory" to locate this information.
251# DATABASE_README, Postfix lookup table overview
252#
253# LICENSE
254# The Secure Mailer license must be distributed with this
255# software.
256#
257# AUTHOR(S)
258# Wietse Venema
259# IBM T.J. Watson Research
260# P.O. Box 704
261# Yorktown Heights, NY 10598, USA
262#
263# Wietse Venema
264# Google, Inc.
265# 111 8th Avenue
266# New York, NY 10011, USA
267#
268# ALIASES(5)