5 .TH MH-TAILOR %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
7 mh-tailor, mts.conf \- mail transport customization for nmh message handler
13 defines run-time options for those
15 programs which interact (in some form) with the message transport system.
16 At present, these (user) programs are:
27 Each option should be given on a single line. Blank lines and lines
28 which begin with `#' are ignored. The options available along with
29 default values and a description of their meanings are listed below:
33 The mail transport method to use. The two acceptable options are
35 (which is the default), and
40 this will enable a direct SMTP (simple mail transport
41 protocol) interface in
43 When sending mail, instead of passing the
44 message to the mail transport agent,
46 will open a socket connection
47 to the mail port on the machine specified in the
55 will send messages by forking a
58 Currently it will still speak SMTP with this local
67 considers local. It should typically be a fully
68 qualified hostname. If this is not set, depending on the version of
71 will query the system for this value
72 (e.g. uname, gethostname, etc.), and attempt to fully qualify this
75 If you are using POP to retrieve new messages, you may want to set this
76 value to the name of the POP server, so that outgoing message appear to
77 have originated on the POP server.
82 If this is set, a `.' followed by this string will be appended to your
85 This should only be needed, if for some reason
88 fully qualify the hostname returned by the system (e.g. uname,
94 This option specifies the host name that
101 command, when posting mail. If not
102 set, the default is to use the host name that
107 above). If this option is set, but empty, no
109 command will be given.
113 command is required by RFC\-821, many SMTP servers
114 do not require it. Early versions of
116 will fail if the hostname
119 command is the local host. Later versions of
121 will complain if you omit the
125 find out what your system expects and set this field if needed.
130 This option is only used for UUCP mail. It specifies the name of the
131 local host in the UUCP \*(lqdomain\*(rq. If not set, depending
132 on the version of UNIX you're running,
134 will query the system
135 for this value. This has no equivalent in the
144 The directory where maildrops are kept. If this option is set, but empty,
145 the user's home directory is used. This overrides the default value
146 chosen at the time of compilation.
151 The name of the maildrop file in the directory where maildrops are kept.
152 If this is empty, the user's login name is used. This overrides the default
153 value (which is empty).
157 \&\\001\\001\\001\\001\\n
159 The beginning-of-message delimiter for maildrops.
163 \&\\001\\001\\001\\001\\n
165 The end-of-message delimiter for maildrops.
170 This directive controls three different types of email address masquerading.
171 The three possible values, which may be specified in any combination on the
172 line, separated by spaces, are \*(lqdraft_from\*(rq, \*(lqmmailid\*(rq, and
173 \*(lqusername_extension\*(rq.
175 \*(lqmmailid\*(rq was the only type of masquerading in the original MH package, and
176 apparently stands for \*(lqmasquerade mail identification\*(rq. This type of
177 masquerading keys off of the GECOS field of the passwd file. When enabled,
179 will check if the user's pw_gecos field in the passwd file is of the
183 Full Name <fakeusername>
186 If it is, the internal
188 routines that find the username and full name
189 of that user will return \*(lqfakeusername\*(rq and \*(lqFull Name\*(rq respectively. This is
190 useful if you want the messages you send to always appear to come from the name
191 of an MTA alias rather than your actual account name. For instance, many
192 organizations set up \*(lqFirst.Last\*(rq sendmail aliases for all users. If this is
193 the case, the GECOS field for each user should look like:
196 First [Middle] Last <First.Last>
199 \*(lqusername_extension\*(rq, when specified on the \*(lqmasquerade:\*(rq line, allows a second
200 type of username masquerading. If the user sets the
201 .B $USERNAME_EXTENSION
202 environment variable, its value will be appended to the actual login name. For
203 instance, if I am \*(lqdan@company.com\*(rq, and I set
204 .B $USERNAME_EXTENSION
205 to \*(lq\-www\*(rq, my mail will appear to come from \*(lqdan\-www@company.com\*(rq. This is meant
206 to interact with qmail's \*(lquser\-extension\*(rq feature, where mail sent to
210 Likewise, those using
211 versions of sendmail for which \*(lqplussed user\*(rq processing is active can set
212 .B $USERNAME_EXTENSION
213 to \*(lq+\fIstring\fR\*(rq. These MTA features are useful
214 because they allow one to use different email addresses in different situations
215 (to aid in automatic mail filtering or in determining where spammers got one's
216 address) while only actually having a single account. Note that
217 .B $USERNAME_EXTENSION
218 is only appended to the username when \fIpost\fR is
219 generating \*(lq[Resent\-]From:\*(rq lines and the SMTP envelope
222 for instance, will not try to read from a maildrop file called \*(lqdan\-www\*(rq (to
223 recall the earlier example).
225 \*(lqdraft_from\*(rq controls the most powerful type of address masquerading. Normally,
226 when a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
229 rather than constructing its own. However, to discourage email forgery, the
230 SMTP envelope \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
231 When \*(lqdraft_from\*(rq is turned on, though, the envelope \*(lqFrom:\*(rq will use the
232 address specified in the draft, and there will be no \*(lqSender:\*(rq header. This is
233 useful when a user wants to pretend to be sending mail \*(lqdirectly\*(rq from a remote
234 POP3 account, or when remote mail robots incorrectly use the envelope \*(lqFrom:\*(rq in
235 preference to the body \*(lqFrom:\*(rq (or refuse to take action when the two don't
236 match). Note that the MTA may still reveal the user's real identity (e.g.
238 \*(lqX\-Authentication\-Warning:\*(rq header).
242 %libdir%/maildelivery
244 The name of the system-wide default
255 The highest user-id which should NOT receive mail addressed to
261 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
262 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
263 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
264 This is useful for handling admin, dummy, and guest logins.
267 These options are only available if you set
275 The exceptions file for /etc/hosts used by
278 official names. The format of this file is quite simple:
281 Comments are surrounded by sharp (`#') and newline.
283 Words are surrounded by white space.
285 The first word on the line is the official name of a host.
287 All words following the official names are aliases for that host.
293 A lists of hosts and networks which to look for SMTP servers when
294 posting local mail. It turns out this is a major win for hosts which
295 don't run an message transport system. The value of
297 should be one or more items. Each item is the name of a host which
298 is (hopefully) running a SMTP server.
300 This option is only available if you set
312 .SS "Post Office Protocol"
313 This option is only available if you have compiled
315 with POP support enabled (i.e., \*(lq--enable-pop\*(rq).
319 The name of the default POP service host. If this is not set, then
321 looks in the standard maildrop areas for waiting mail, otherwise
322 the named POP service host is consulted.
324 \" .SS "BBoards Delivery"
325 \" This option is only available if you compiled \fInmh\fP with
326 \" \*(lqbbdelivery:\ on\*(rq.
330 \" The local BBoards domain (a UCI hack).
333 \" .SS "BBoards & The POP"
334 \" These options are only available if you compiled \fInmh\fP with
335 \" \*(lqbboards:\ pop\*(rq and \*(lqpop:\ on\*(rq.
340 \" The POP service host which also acts as a BBoard server. This variable
341 \" should be set on the POP BBoards client host.
346 \" The guest account on the POP/BB service host. This should be a different
347 \" login ID than either the POP user or the BBoards user. (The user-id
348 \" \*(lqftp\*(rq is highly recommended.) This variable should be set on
349 \" both the POP BBoards client and service hosts.
353 \" %etcdir%/hosts.popbb
355 \" A file containing of lists of hosts that are allowed to use the POP
356 \" facility to access BBoards using the guest account. If this file is not
357 \" present, then no check is made. This variable should be set on the POP
358 \" BBoards service host.
361 \" .SS "BBoards & The NNTP"
362 \" This option is only available if you compiled \fInmh\fP with
363 \" \*(lqbboards:\ nntp\*(rq and \*(lqpop:\ on\*(rq.
367 \" The host which provides the NNTP service. This variable should be set
368 \" on the NNTP BBoards client host.
371 A few words on locking:
373 has several methods for creating locks
374 on files. When configuring
376 you will need to decide on the
377 locking style and locking directory (if any). The first controls the
378 method of locking, the second says where lock files should be created.
382 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
385 system call; use \*(lq--with-locking=lockf\*(rq if
388 system call; or use \*(lq--with-locking=fcntl\*(rq
389 if you want to use the
391 system call for kernel-level locking.
393 Instead of kernel locking, you can configure
395 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
397 a file should be created whose existence means \*(lqlocked\*(rq and
398 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
399 constructed by appending \*(lq.lock\*(rq to the name of the file being
402 is not specified, lock files will be created
403 in the directory where the file being locked resides. Otherwise, lock
404 files will be created in the directory specified by
409 you should see how locking is done at
410 your site, and set the appropriate values.
415 .ta \w'%etcdir%/ExtraBigFileName 'u
416 ^%etcdir%/mts.conf~^nmh mts configuration file
419 .SH "PROFILE COMPONENTS"