]>
Commit | Line | Data |
---|---|---|
3796e3d5 MT |
1 | # RELOCATED(5) RELOCATED(5) |
2 | # | |
3 | # NAME | |
4 | # relocated - Postfix relocated table format | |
5 | # | |
6 | # SYNOPSIS | |
7 | # postmap /etc/postfix/relocated | |
8 | # | |
9 | # DESCRIPTION | |
10 | # The optional relocated(5) table provides the information | |
11 | # that is used in "user has moved to new_location" bounce | |
12 | # messages. | |
13 | # | |
14 | # Normally, the relocated(5) table is specified as a text | |
15 | # file that serves as input to the postmap(1) command. The | |
16 | # result, an indexed file in dbm or db format, is used for | |
17 | # fast searching by the mail system. Execute the command | |
18 | # "postmap /etc/postfix/relocated" in order to rebuild the | |
19 | # indexed file after changing the relocated table. | |
20 | # | |
21 | # When the table is provided via other means such as NIS, | |
22 | # LDAP or SQL, the same lookups are done as for ordinary | |
23 | # indexed files. | |
24 | # | |
25 | # Alternatively, the table can be provided as a regular- | |
26 | # expression map where patterns are given as regular expres- | |
27 | # sions, or lookups can be directed to TCP-based server. In | |
28 | # that case, the lookups are done in a slightly different | |
29 | # way as described below under "REGULAR EXPRESSION TABLES" | |
30 | # and "TCP-BASED TABLES". | |
31 | # | |
32 | # Table lookups are case insensitive. | |
33 | # | |
34 | # TABLE FORMAT | |
35 | # The input format for the postmap(1) command is as follows: | |
36 | # | |
37 | # o An entry has one of the following form: | |
38 | # pattern new_location | |
39 | # Where new_location specifies contact information | |
40 | # such as an email address, or perhaps a street | |
41 | # address or telephone number. | |
42 | # | |
43 | # o Empty lines and whitespace-only lines are ignored, | |
44 | # as are lines whose first non-whitespace character | |
45 | # is a `#'. | |
46 | # | |
47 | # o A logical line starts with non-whitespace text. A | |
48 | # line that starts with whitespace continues a logi- | |
49 | # cal line. | |
50 | # | |
51 | # TABLE SEARCH ORDER | |
52 | # With lookups from indexed files such as DB or DBM, or from | |
53 | # networked tables such as NIS, LDAP or SQL, patterns are | |
54 | # tried in the order as listed below: | |
55 | # | |
56 | # user@domain | |
57 | # Matches user@domain. This form has precedence over | |
58 | # all other forms. | |
59 | # | |
60 | # user Matches user@site when site is $myorigin, when site | |
61 | # is listed in $mydestination, or when site is listed | |
62 | # in $inet_interfaces or $proxy_interfaces. | |
63 | # | |
64 | # @domain | |
65 | # Matches other addresses in domain. This form has | |
66 | # the lowest precedence. | |
67 | # | |
68 | # ADDRESS EXTENSION | |
69 | # When a mail address localpart contains the optional recip- | |
70 | # ient delimiter (e.g., user+foo@domain), the lookup order | |
71 | # becomes: user+foo@domain, user@domain, user+foo, user, and | |
72 | # @domain. | |
73 | # | |
74 | # REGULAR EXPRESSION TABLES | |
75 | # This section describes how the table lookups change when | |
76 | # the table is given in the form of regular expressions or | |
77 | # when lookups are directed to a TCP-based server. For a | |
78 | # description of regular expression lookup table syntax, see | |
79 | # regexp_table(5) or pcre_table(5). For a description of the | |
80 | # TCP client/server table lookup protocol, see tcp_table(5). | |
81 | # This feature is not available up to and including Postfix | |
82 | # version 2.2. | |
83 | # | |
84 | # Each pattern is a regular expression that is applied to | |
85 | # the entire address being looked up. Thus, user@domain mail | |
86 | # addresses are not broken up into their user and @domain | |
87 | # constituent parts, nor is user+foo broken up into user and | |
88 | # foo. | |
89 | # | |
90 | # Patterns are applied in the order as specified in the ta- | |
91 | # ble, until a pattern is found that matches the search | |
92 | # string. | |
93 | # | |
94 | # Results are the same as with indexed file lookups, with | |
95 | # the additional feature that parenthesized substrings from | |
96 | # the pattern can be interpolated as $1, $2 and so on. | |
97 | # | |
98 | # TCP-BASED TABLES | |
99 | # This section describes how the table lookups change when | |
100 | # lookups are directed to a TCP-based server. For a descrip- | |
101 | # tion of the TCP client/server lookup protocol, see tcp_ta- | |
102 | # ble(5). This feature is not available up to and including | |
103 | # Postfix version 2.2. | |
104 | # | |
105 | # Each lookup operation uses the entire address once. Thus, | |
106 | # user@domain mail addresses are not broken up into their | |
107 | # user and @domain constituent parts, nor is user+foo broken | |
108 | # up into user and foo. | |
109 | # | |
110 | # Results are the same as with indexed file lookups. | |
111 | # | |
112 | # BUGS | |
113 | # The table format does not understand quoting conventions. | |
114 | # | |
115 | # CONFIGURATION PARAMETERS | |
116 | # The following main.cf parameters are especially relevant. | |
117 | # The text below provides only a parameter summary. See | |
118 | # postconf(5) for more details including examples. | |
119 | # | |
120 | # relocated_maps | |
121 | # List of lookup tables for relocated users or sites. | |
122 | # | |
123 | # Other parameters of interest: | |
124 | # | |
125 | # inet_interfaces | |
126 | # The network interface addresses that this system | |
127 | # receives mail on. You need to stop and start Post- | |
128 | # fix when this parameter changes. | |
129 | # | |
130 | # mydestination | |
131 | # List of domains that this mail system considers | |
132 | # local. | |
133 | # | |
134 | # myorigin | |
135 | # The domain that is appended to locally-posted mail. | |
136 | # | |
137 | # proxy_interfaces | |
138 | # Other interfaces that this machine receives mail on | |
139 | # by way of a proxy agent or network address transla- | |
140 | # tor. | |
141 | # | |
142 | # SEE ALSO | |
143 | # trivial-rewrite(8), address resolver | |
144 | # postmap(1), Postfix lookup table manager | |
145 | # postconf(5), configuration parameters | |
146 | # | |
147 | # README FILES | |
148 | # Use "postconf readme_directory" or "postconf html_direc- | |
149 | # tory" to locate this information. | |
150 | # DATABASE_README, Postfix lookup table overview | |
151 | # ADDRESS_REWRITING_README, address rewriting guide | |
152 | # | |
153 | # LICENSE | |
154 | # The Secure Mailer license must be distributed with this | |
155 | # software. | |
156 | # | |
157 | # AUTHOR(S) | |
158 | # Wietse Venema | |
159 | # IBM T.J. Watson Research | |
160 | # P.O. Box 704 | |
161 | # Yorktown Heights, NY 10598, USA | |
162 | # | |
163 | # RELOCATED(5) |