4 .TH MH-TAILOR %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
6 mh-tailor, mts.conf \- mail transport customization for nmh message handler
12 defines run-time options for those
14 programs which interact (in some form) with the message transport system.
15 At present, these (user) programs are:
26 Each option should be given on a single line. Blank lines and lines
27 which begin with `#' are ignored. The options available along with
28 default values and a description of their meanings are listed below:
32 The mail transport method to use. The two acceptable options are
34 (which is the default), and
39 this will enable a direct SMTP (simple mail transport
40 protocol) interface in
42 When sending mail, instead of passing the
43 message to the mail transport agent,
45 will open a socket connection
46 to the mail port on the machine specified in the
54 will send messages by forking a
57 Currently it will still speak SMTP with this local
66 considers local. It should typically be a fully
67 qualified hostname. If this is not set, depending on the version of
70 will query the system for this value
71 (e.g. uname, gethostname, etc.), and attempt to fully qualify this
74 If you are using POP to retrieve new messages, you may want to set this
75 value to the name of the POP server, so that outgoing message appear to
76 have originated on the POP server.
81 If this is set, a `.' followed by this string will be appended to your
84 This should only be needed, if for some reason
87 fully qualify the hostname returned by the system (e.g. uname,
93 This option specifies the host name that
100 command, when posting mail. If not
101 set, the default is to use the host name that
106 above). If this option is set, but empty, no
108 command will be given.
112 command is required by RFC\-821, many SMTP servers
113 do not require it. Early versions of
115 will fail if the hostname
118 command is the local host. Later versions of
120 will complain if you omit the
124 find out what your system expects and set this field if needed.
129 This option is only used for UUCP mail. It specifies the name of the
130 local host in the UUCP \*(lqdomain\*(rq. If not set, depending
131 on the version of UNIX you're running,
133 will query the system
134 for this value. This has no equivalent in the
143 The directory where maildrops are kept. If this option is set, but empty,
144 the user's home directory is used. This overrides the default value
145 chosen at the time of compilation.
150 The name of the maildrop file in the directory where maildrops are kept.
151 If this is empty, the user's login name is used. This overrides the default
152 value (which is empty).
156 \&\\001\\001\\001\\001\\n
158 The beginning-of-message delimiter for maildrops.
162 \&\\001\\001\\001\\001\\n
164 The end-of-message delimiter for maildrops.
169 This directive controls three different types of email address masquerading.
170 The three possible values, which may be specified in any combination on the
171 line, separated by spaces, are \*(lqdraft_from\*(rq, \*(lqmmailid\*(rq, and
172 \*(lqusername_extension\*(rq.
174 \*(lqmmailid\*(rq was the only type of masquerading in the original MH package, and
175 apparently stands for \*(lqmasquerade mail identification\*(rq. This type of
176 masquerading keys off of the GECOS field of the passwd file. When enabled,
178 will check if the user's pw_gecos field in the passwd file is of the
182 Full Name <fakeusername>
185 If it is, the internal
187 routines that find the username and full name
188 of that user will return \*(lqfakeusername\*(rq and \*(lqFull Name\*(rq respectively. This is
189 useful if you want the messages you send to always appear to come from the name
190 of an MTA alias rather than your actual account name. For instance, many
191 organizations set up \*(lqFirst.Last\*(rq sendmail aliases for all users. If this is
192 the case, the GECOS field for each user should look like:
195 First [Middle] Last <First.Last>
198 \*(lqusername_extension\*(rq, when specified on the \*(lqmasquerade:\*(rq line, allows a second
199 type of username masquerading. If the user sets the
200 .B $USERNAME_EXTENSION
201 environment variable, its value will be appended to the actual login name. For
202 instance, if I am \*(lqdan@company.com\*(rq, and I set
203 .B $USERNAME_EXTENSION
204 to \*(lq\-www\*(rq, my mail will appear to come from \*(lqdan\-www@company.com\*(rq. This is meant
205 to interact with qmail's \*(lquser\-extension\*(rq feature, where mail sent to
209 Likewise, those using
210 versions of sendmail for which \*(lqplussed user\*(rq processing is active can set
211 .B $USERNAME_EXTENSION
212 to \*(lq+\fIstring\fR\*(rq. These MTA features are useful
213 because they allow one to use different email addresses in different situations
214 (to aid in automatic mail filtering or in determining where spammers got one's
215 address) while only actually having a single account. Note that
216 .B $USERNAME_EXTENSION
217 is only appended to the username when \fIpost\fR is
218 generating \*(lq[Resent\-]From:\*(rq lines and the SMTP envelope
221 for instance, will not try to read from a maildrop file called \*(lqdan\-www\*(rq (to
222 recall the earlier example).
224 \*(lqdraft_from\*(rq controls the most powerful type of address masquerading. Normally,
225 when a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
228 rather than constructing its own. However, to discourage email forgery, the
229 SMTP envelope \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
230 When \*(lqdraft_from\*(rq is turned on, though, the envelope \*(lqFrom:\*(rq will use the
231 address specified in the draft, and there will be no \*(lqSender:\*(rq header. This is
232 useful when a user wants to pretend to be sending mail \*(lqdirectly\*(rq from a remote
233 POP3 account, or when remote mail robots incorrectly use the envelope \*(lqFrom:\*(rq in
234 preference to the body \*(lqFrom:\*(rq (or refuse to take action when the two don't
235 match). Note that the MTA may still reveal the user's real identity (e.g.
237 \*(lqX\-Authentication\-Warning:\*(rq header).
241 %libdir%/maildelivery
243 The name of the system-wide default
254 The highest user-id which should NOT receive mail addressed to
260 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
261 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
262 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
263 This is useful for handling admin, dummy, and guest logins.
265 This option is only available if you set
277 A few words on locking:
279 has several methods for creating locks
280 on files. When configuring
282 you will need to decide on the
283 locking style and locking directory (if any). The first controls the
284 method of locking, the second says where lock files should be created.
288 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
291 system call; use \*(lq--with-locking=lockf\*(rq if
294 system call; or use \*(lq--with-locking=fcntl\*(rq
295 if you want to use the
297 system call for kernel-level locking.
299 Instead of kernel locking, you can configure
301 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
303 a file should be created whose existence means \*(lqlocked\*(rq and
304 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
305 constructed by appending \*(lq.lock\*(rq to the name of the file being
308 is not specified, lock files will be created
309 in the directory where the file being locked resides. Otherwise, lock
310 files will be created in the directory specified by
315 you should see how locking is done at
316 your site, and set the appropriate values.
321 .ta \w'%etcdir%/ExtraBigFileName 'u
322 ^%etcdir%/mts.conf~^nmh mts configuration file
325 .SH "PROFILE COMPONENTS"
projects / mmh / blob