1RELOCATED(5) File Formats Manual RELOCATED(5)
2
6 relocated - Postfix relocated table format
7
9 postmap /etc/postfix/relocated
10
12 The optional relocated(5) table provides the information that is used
13 in "user has moved to new_location" bounce messages.
14 Normally, the relocated(5) table is specified as a text file that
16 serves as input to the postmap(1) command. The result, an indexed file
17 in dbm or db format, is used for fast searching by the mail system. Ex‐
18 ecute the command "postmap /etc/postfix/relocated" to rebuild an in‐
19 dexed file after changing the corresponding relocated table.
20 When the table is provided via other means such as NIS, LDAP or SQL,
22 the same lookups are done as for ordinary indexed files.
23 Alternatively, the table can be provided as a regular-expression map
25 where patterns are given as regular expressions, or lookups can be di‐
26 rected to a TCP-based server. In those case, the lookups are done in a
27 slightly different way as described below under "REGULAR EXPRESSION TA‐
28 BLES" or "TCP-BASED TABLES".
29 Table lookups are case insensitive.
31
33 The search string is folded to lowercase before database lookup. As of
34 Postfix 2.3, the search string is not case folded with database types
35 such as regexp: or pcre: whose lookup fields can match both upper and
36 lower case.
37
39 The input format for the postmap(1) command is as follows:
40 • An entry has one of the following form:
42 pattern new_location
44 Where new_location specifies contact information such as an
46 email address, or perhaps a street address or telephone number.
47 • Empty lines and whitespace-only lines are ignored, as are lines
49 whose first non-whitespace character is a `#'.
50 • A logical line starts with non-whitespace text. A line that
52 starts with whitespace continues a logical line.
53
55 With lookups from indexed files such as DB or DBM, or from networked
56 tables such as NIS, LDAP or SQL, patterns are tried in the order as
57 listed below:
58 user@domain
60 Matches user@domain. This form has precedence over all other
61 forms.
62 user Matches user@site when site is $myorigin, when site is listed in
64 $mydestination, or when site is listed in $inet_interfaces or
65 $proxy_interfaces.
66 @domain
68 Matches other addresses in domain. This form has the lowest
69 precedence.
70
72 When a mail address localpart contains the optional recipient delimiter
73 (e.g., user+foo@domain), the lookup order becomes: user+foo@domain,
74 user@domain, user+foo, user, and @domain.
75
77 This section describes how the table lookups change when the table is
78 given in the form of regular expressions or when lookups are directed
79 to a TCP-based server. For a description of regular expression lookup
80 table syntax, see regexp_table(5) or pcre_table(5). For a description
81 of the TCP client/server table lookup protocol, see tcp_table(5). This
82 feature is available in Postfix 2.5 and later.
83 Each pattern is a regular expression that is applied to the entire ad‐
85 dress being looked up. Thus, user@domain mail addresses are not broken
86 up into their user and @domain constituent parts, nor is user+foo bro‐
87 ken up into user and foo.
88 Patterns are applied in the order as specified in the table, until a
90 pattern is found that matches the search string.
91 Results are the same as with indexed file lookups, with the additional
93 feature that parenthesized substrings from the pattern can be interpo‐
94 lated as $1, $2 and so on.
95
97 This section describes how the table lookups change when lookups are
98 directed to a TCP-based server. For a description of the TCP
99 client/server lookup protocol, see tcp_table(5). This feature is
100 available in Postfix 2.5 and later.
101 Each lookup operation uses the entire address once. Thus, user@domain
103 mail addresses are not broken up into their user and @domain con‐
104 stituent parts, nor is user+foo broken up into user and foo.
105 Results are the same as with indexed file lookups.
107
109 The table format does not understand quoting conventions.
110
112 The following main.cf parameters are especially relevant. The text be‐
113 low provides only a parameter summary. See postconf(5) for more details
114 including examples.
115 relocated_maps (empty)
117 Optional lookup tables with new contact information for users or
118 domains that no longer exist.
119 Other parameters of interest:
121 inet_interfaces (all)
123 The network interface addresses that this mail system receives
124 mail on.
125 mydestination ($myhostname, localhost.$mydomain, localhost)
127 The list of domains that are delivered via the $local_transport
128 mail delivery transport.
129 myorigin ($myhostname)
131 The domain name that locally-posted mail appears to come from,
132 and that locally posted mail is delivered to.
133 proxy_interfaces (empty)
135 The network interface addresses that this mail system receives
136 mail on by way of a proxy or network address translation unit.
137
139 trivial-rewrite(8), address resolver
140 postmap(1), Postfix lookup table manager
141 postconf(5), configuration parameters
142
144 Use "postconf readme_directory" or "postconf html_directory" to locate
145 this information.
146 DATABASE_README, Postfix lookup table overview
147 ADDRESS_REWRITING_README, address rewriting guide
148
150 The Secure Mailer license must be distributed with this software.
151
153 Wietse Venema
154 IBM T.J. Watson Research
155 P.O. Box 704
156 Yorktown Heights, NY 10598, USA
157 Wietse Venema
159 Google, Inc.
160 111 8th Avenue
161 New York, NY 10011, USA
162 RELOCATED(5)