summaryrefslogtreecommitdiff
path: root/gnu/dist/postfix/html/virtual.5.html
blob: 91f57e9b7bd5a91cdf252f1578817729b4172aa9 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
<html> <head> </head> <body> <pre>



VIRTUAL(5)                                             VIRTUAL(5)


<b>NAME</b>
       virtual - format of Postfix virtual table

<b>SYNOPSIS</b>
       <b>postmap</b> <b>/etc/postfix/virtual</b>

<b>DESCRIPTION</b>
       The  optional  <b>virtual</b>  table  specifies  redirections for
       local and non-local recipients or  domains.  The  redirec-
       tions  are used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon. The redirections
       are recursive.

       The <b>virtual</b> redirection is applied only to  the  recipient
       envelope  address,  and  does  not affect message headers.
       Think Sendmail rule set <b>S0</b>, if you like. Use  <a href="canonical.5.html"><b>canonical</b>(5)</a>
       mapping  to  rewrite header and envelope addresses in gen-
       eral.

       The file serves as input to the  <a href="postmap.1.html"><b>postmap</b>(1)</a>  command.  The
       result,  an  indexed file in <b>dbm</b> or <b>db</b> format, is used for
       fast searching by the mail system. After an update it  may
       take  a  minute  or  so before the change becomes visible.
       Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay.

       Typical support for a virtual domain looks like  the  fol-
       lowing:

           <i>virtual.domain</i>       <i>anything</i> (right-hand content does not matter)
           <i>user1@virtual.domain</i> <i>address1</i>
           <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i>

       With this, the SMTP server accepts mail for <i>virtual.domain</i>
       and rejects mail for <i>unknown</i>@<i>virtual.domain</i> as  undeliver-
       able.

       The  format  of  the virtual table is as follows, mappings
       being tried in the order as listed in this manual page:

       blanks and comments
              Blank lines are ignored,  as  are  lines  beginning
              with `#'.

       <i>user</i>@<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i>
              Mail  for  <i>user</i>@<i>domain</i>  is  redirected  to <i>address</i>.
              This form has the highest precedence.

       <i>user</i> <i>address,</i> <i>address,</i> <i>...</i>
              Mail for <i>user</i>@<i>site</i> is redirected  to  <i>address</i>  when
              <i>site</i>  is equal to $<b>myorigin</b>, when <i>site</i> is listed in
              $mydestination,   or   when   it   is   listed   in
              $<i>inet_interfaces</i>.

              This  functionality  overlaps with functionality of
              the local <i>alias</i>(5) database. The difference is that



                                                                1





VIRTUAL(5)                                             VIRTUAL(5)


              <b>virtual</b>   mapping   can  be  applied  to  non-local
              addresses.

       @<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i>
              Mail for  any  user  in  <i>domain</i>  is  redirected  to
              <i>address</i>.  This form has the lowest precedence.

       In  all the above forms, when <i>address</i> has the form @<i>other-</i>
       <i>domain</i>, the result is the same user in <i>otherdomain</i>.   This
       works for the first address in the expansion only.

<b>ADDRESS</b> <b>EXTENSION</b>
       When  the search fails, and the address localpart contains
       the optional recipient delimiter (e.g.,  <i>user+foo</i>@<i>domain</i>),
       the  search  is  repeated for the unextended address (e.g.
       <i>user</i>@<i>domain</i>), and the unmatched address extension is prop-
       agated  to the result of expansion. The matching order is:
       <i>user+foo</i>@<i>domain</i>, <i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>.

<b>BUGS</b>
       The  table format does not understand quoting conventions.

<b>CONFIGURATION</b> <b>PARAMETERS</b>
       The following <b>main.cf</b> parameters are  especially  relevant
       to  this  topic.  See  the Postfix <b>main.cf</b> file for syntax
       details and for default values.  Use  the  <b>postfix</b>  <b>reload</b>
       command after a configuration change.

       <b>virtual</b><i>_</i><b>maps</b>
              List of virtual mapping tables.

       Other parameters of interest:

       <b>inet</b><i>_</i><b>interfaces</b>
              The  network  interface  addresses that this system
              receives mail on.

       <b>mydestination</b>
              List of domains that  this  mail  system  considers
              local.

       <b>myorigin</b>
              The domain that is appended to locally-posted mail.

       <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b>
              Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b>
              addresses.

<b>SEE</b> <b>ALSO</b>
       <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail
       <a href="postmap.1.html">postmap(1)</a> create mapping table

<b>LICENSE</b>
       The  Secure  Mailer  license must be distributed with this



                                                                2





VIRTUAL(5)                                             VIRTUAL(5)


       software.

<b>AUTHOR(S)</b>
       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA


















































                                                                3


</pre> </body> </html>