1 .TH MH-ALIAS %manext5% 2014-04-18 "%nmhversion%"
6 mh-alias \- format of nmh email-address alias files
11 alias file takes one of the following forms:
43 .IR address-group " := " address-list
46 .IR address-list " := " address
47 .RI " | " address-list ", " address
51 Continuation lines end with \*(lq\\\*(rq followed by a newline
52 character. This also applies to comment lines. Thus, the line following a
53 \*(lq\\\*(rq-terminated
54 comment line is a continuation of
61 Alias file contents are case-insensitive, with the exception
62 of filesystem path names.
64 If the line starts with a \*(lq<\*(rq, the file named after the \*(lq<\*(rq is
65 read for more alias definitions. The reading is done recursively, so a
66 \*(lq<\*(rq may occur in the beginning of an alias file with the expected results.
70 starts with a \*(lq<\*(rq, the file named after the
71 \*(lq<\*(rq is read and its contents are added to the
75 In match, a trailing \*(lq*\*(rq on an alias will match just about anything
78 An approximation of the way aliases are resolved at posting time is:
80 Build a list of all addresses from the message to be delivered,
81 eliminating duplicate addresses.
83 For those addresses in the message that have no host specified,
84 perform alias resolution.
86 For each line in the alias file, compare \*(lqalias\*(rq against all of
87 the existing addresses. If a match, remove the matched \*(lqalias\*(rq
88 from the address list, and add each new address in the address-group to
89 the address list if it is not already on the list. The alias itself is
90 not usually output, rather the address-group that the alias maps to is
91 output instead. If \*(lqalias\*(rq is terminated with a \*(lq;\*(rq instead of
92 a \*(lq:\*(rq, then both the \*(lqalias\*(rq and the address are output in the
93 correct format (with the alias quoted if necessary and the address
98 file is read line by line, forward references work, but
99 backward references are not recognized.
105 <%nmhetcdir%/BBoardAliases
106 sgroup: fred, fear, freida
107 fred: frated@UCI.example
108 b-people: Blind List: bill, betty
109 Unix\-committee: <unix.aliases
114 The first line says that more aliases should immediately be read from
116 .BR %nmhetcdir%/BBoardAliases .
117 Next, \*(lqsgroup\*(rq is defined as an alias for three names,
118 and one of them, \*(lqfred\*(rq,
119 is a forward reference to another alias for \*(lqfrated@UCI.example\*(rq.
121 The alias \*(lqb-people\*(rq is a blind list which includes the addresses
122 \*(lqbill\*(rq and \*(lqbetty\*(rq; the message will be delivered to those
123 addresses, but the message header will show only \*(lqBlind List: ;\*(rq
124 (not the addresses). The alias must not be terminated with, or contain,
126 Note that blind lists are not supported with the
128 mail transport method.
130 The definition of \*(lqUnix\-committee\*(rq is given by
138 .RI \*(lqnews. anything \*(rq
139 is aliased to \*(lqnews\*(rq;
140 the full stop is just another literal character.
141 .SH "PROFILE COMPONENTS"
147 %nmhetcdir%/MailAliases
148 System-wide default alias file.
157 Although the forward-referencing semantics of
159 files prevent recursion, the
161 directive may defeat this.
162 Since the number of file descriptors is finite, such
163 infinite recursion will terminate with a meaningless diagnostic when
164 all the fds are used up.
166 Earlier versions of this man page showed a semicolon at the end of the
167 blind list example. That caused the preceding alias to not be
168 expanded. There must not be a semicolon at the end of, or within, the
169 address group of a blind list.
171 will append the semicolon to the blind list name.