3 newaliases \- create a forwarding database from /etc/aliases
10 forwarding instructions from
12 and converts them into a forwarding database in
13 .BR /etc/aliases.cdb .
14 The forwarding database can be used by
19 writes the forwarding database to
24 .BR /etc/aliases.cdb .
25 If there is a problem creating
26 .BR /etc/aliases.tmp ,
31 Deliveries can continue using
41 makes no attempt to protect against
42 simultaneous updates of
43 .BR /etc/aliases.cdb .
44 .SH "INSTRUCTION FORMAT"
58 should be forwarded to
63 .B COMPATIBILITY WARNING:
65 does not support file deliveries.
66 You can use the file delivery mechanism described in
70 The simplest type of forwarding instruction
79 will be forwarded to the recipient address
81 Addresses are compared to
83 without regard to case.
85 Forwarding instructions are cumulative.
91 will be forwarded the same way as
94 For example, with the following instructions,
96 .B postmaster@heaven.af.mil
99 will be delivered to Bob:
102 postmaster@heaven.af.mil: bob@heaven.af.mil
106 root@heaven.af.mil: postmaster@heaven.af.mil
109 .B COMPATIBILITY WARNING:
114 can override usernames.
120 .BR ~alias/.qmail-default ,
121 it will not see addresses that are controlled by other users.
127 .B COMPATIBILITY WARNING:
130 do various strange things with circular alias definitions.
137 .B COMPATIBILITY WARNING:
138 If there are several forwarding instructions for a single
143 will silently use the first instruction.
148 for one user at one host,
150 for all users at one host, or
152 for one user at all hosts.
154 .B COMPATIBILITY WARNING:
158 it does not support per-host aliases.
164 but it then treats it the same way as
166 applying to all local hosts and virtual domains.
167 .SH "ADDRESS FORMATS"
170 are parsed the same way as addresses in RFC 822 message headers.
171 Parenthesized comments and bracketed addresses are permitted:
174 root: bob (Bob, the postmaster)
175 joe: Joe Shmoe <shmoe@heaven.af.mil>
178 Addresses with special characters must be quoted:
181 fred: "spaced out mailbox"@heaven.af.mil
184 Address groups are not permitted,
185 since colons have a different use in
188 Any recipient address without a fully qualified domain name is
194 mechanisms described in
195 .BR qmail-header (5).
197 .B COMPATIBILITY WARNING:
199 handling of quotes and backslashes violates RFC 821 and RFC 822,
200 and is not supported by
205 lets each user manage several addresses,
206 so there is no need for a special syntax to get around forwarding.
207 .SH "MULTIPLE RECIPIENTS"
208 An instruction may list more than one recipient address:
211 alias: recip1, recip2, recip3
216 will be forwarded to all of the addresses.
218 A forwarding instruction may be split across several lines.
219 Each line past the first must either (1) begin with space or tab
234 .B COMPATIBILITY WARNING:
236 requires the colon to be on the first line
237 of a multi-line forwarding instruction.
239 doesn't care whether the colon is present at all.
241 .B COMPATIBILITY WARNING:
243 does not permit blank lines in the middle of continuations.
244 This has the undesirable effect that a blank line behaves differently
245 from a line containing a single space.
249 that begins with # is ignored:
255 A comment may be split across several lines.
256 Each line past the first must either (1) begin with space or tab
259 .B COMPATIBILITY WARNING:
261 does not permit continuations of comment lines.
263 If a recipient address does not contain a domain name,
264 and begins with a vertical bar,
266 takes the rest of the address as a program to run:
269 weather: "|weather-server"
275 when a message arrives for
278 .B COMPATIBILITY WARNING:
279 Internet addresses can legitimately start with
280 a slash or vertical bar.
282 treats anything with an unquoted @ as an address.
283 sendmail appears to have various problems
284 coping with these addresses,
285 and with commands that contain @ signs.
287 .B COMPATIBILITY WARNING:
289 does not allow a vertical bar before double quotes.
291 A recipient address of the form
293 means ``every address listed in
301 for further details.)
309 so the system administrator does not have to run
315 must be world-readable
319 .B COMPATIBILITY WARNING:
322 file is unreadable or nonexistent,
326 defers delivery of the message.
328 .B COMPATIBILITY WARNING:
330 does not permit spaces inside the literal text
335 .B COMPATIBILITY WARNING:
338 before V8 did not strip quotes from
342 If there is an alias for
344 any message forwarded through
346 will have its envelope sender set to
348 so that bounces go back to
351 .B COMPATIBILITY WARNING:
352 When an alias includes the same recipient both inside and outside
355 sends the message twice,
356 once with each envelope sender.
358 sends the message only once;
359 its choice of envelope sender for that recipient
360 depends on the phase of the moon.