4 .TH MH-TAILOR %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
6 mh-tailor, mts.conf \- mail transport configuration 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 three acceptable options are
34 (which is the default),
41 this will enable a direct SMTP (simple mail transport
42 protocol) interface in
44 When sending mail, instead of passing the
45 message to the mail transport agent,
47 will open a socket connection
48 to the mail port on the machine specified in the
56 will send messages by forking a
59 It will still speak SMTP with this local copy of
62 The third alternative,
64 also forks a local copy of
66 but feeds the message directly to it, using
69 This replaces the old, undocumented
71 mechanism and retains some of its limitations, such as lack of
75 \*(lqDcc:\*(rq header field.
82 considers local. It should typically be a fully
83 qualified hostname. If this is not set, depending on the version of
86 will query the system for this value
87 (e.g. uname, gethostname, etc.), and attempt to fully qualify this
90 If you are using POP to retrieve new messages, you may want to set this
91 value to the name of the POP server, so that outgoing message appear to
92 have originated on the POP server.
97 If this is set, a `.' followed by this string will be appended to your
100 This should only be needed, if for some reason
103 fully qualify the hostname returned by the system (e.g. uname,
109 This option specifies the host name that
116 command, when posting mail. If not
117 set, the default is to use the host name that
122 above). If this option is set, but empty, no
124 command will be given.
128 command is required by RFC\-821, many SMTP servers
129 do not require it. Early versions of
131 will fail if the hostname
134 command is the local host. Later versions of
136 will complain if you omit the
140 find out what your system expects and set this field if needed.
145 This option is only used for UUCP mail. It specifies the name of the
146 local host in the UUCP \*(lqdomain\*(rq. If not set, depending
147 on the version of UNIX you're running,
149 will query the system
150 for this value. This has no equivalent in the
159 The directory where maildrops are kept. If this option is set, but empty,
160 the user's home directory is used. This overrides the default value
161 chosen at the time of compilation.
166 The name of the maildrop file in the directory where maildrops are kept.
167 If this is empty, the user's login name is used. This overrides the default
168 value (which is empty).
172 \&\\001\\001\\001\\001\\n
174 The beginning-of-message delimiter for maildrops.
178 \&\\001\\001\\001\\001\\n
180 The end-of-message delimiter for maildrops.
184 %libdir%/maildelivery
186 The name of the system-wide default
197 The highest user-id which should NOT receive mail addressed to
203 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
204 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
205 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
206 This is useful for handling admin, dummy, and guest logins.
209 This option is only available if you set
217 A lists of hosts and networks which to look for SMTP servers when
218 posting non\-local mail. It turns out this is a major win for hosts
219 which don't run an message transport system. The value of
221 should be one or more items. Each item is the name of a host which
222 is (hopefully) running a SMTP server.
224 This option is only available if you set
236 .SS "Post Office Protocol"
237 This option is only available if you have compiled
239 with POP support enabled (i.e., \*(lq--enable-pop\*(rq).
243 The name of the default POP service host. If this is not set, then
245 looks in the standard maildrop areas for waiting mail, otherwise
246 the named POP service host is consulted.
248 \" .SS "BBoards Delivery"
249 \" This option is only available if you compiled \fInmh\fP with
250 \" \*(lqbbdelivery:\ on\*(rq.
254 \" The local BBoards domain (a UCI hack).
257 \" .SS "BBoards & The POP"
258 \" These options are only available if you compiled \fInmh\fP with
259 \" \*(lqbboards:\ pop\*(rq and \*(lqpop:\ on\*(rq.
264 \" The POP service host which also acts as a BBoard server. This variable
265 \" should be set on the POP BBoards client host.
270 \" The guest account on the POP/BB service host. This should be a different
271 \" login ID than either the POP user or the BBoards user. (The user-id
272 \" \*(lqftp\*(rq is highly recommended.) This variable should be set on
273 \" both the POP BBoards client and service hosts.
277 \" %etcdir%/hosts.popbb
279 \" A file containing of lists of hosts that are allowed to use the POP
280 \" facility to access BBoards using the guest account. If this file is not
281 \" present, then no check is made. This variable should be set on the POP
282 \" BBoards service host.
286 A few words on locking:
288 has several methods for creating locks
289 on files. When configuring
291 you will need to decide on the
292 locking style and locking directory (if any). The first controls the
293 method of locking, the second says where lock files should be created.
297 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
300 system call; use \*(lq--with-locking=lockf\*(rq if
303 system call; or use \*(lq--with-locking=fcntl\*(rq
304 if you want to use the
306 system call for kernel-level locking.
308 Instead of kernel locking, you can configure
310 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
312 a file should be created whose existence means \*(lqlocked\*(rq and
313 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
314 constructed by appending \*(lq.lock\*(rq to the name of the file being
315 locked. If \*(lq--enable-lockdir=directory\*(rq
316 is not specified at build time, lock files will be created
317 in the directory where the file being locked resides. Otherwise, lock
318 files will be created in the directory specified by
319 \*(lq--enable-lockdir\*(rq.
323 you should see how locking is done at
324 your site, and set the appropriate values.
329 .ta \w'%etcdir%/ExtraBigFileName 'u
330 ^%etcdir%/mts.conf~^nmh mts configuration file
333 .SH "PROFILE COMPONENTS"
340 As listed above. The path of the mail transport configuration
341 file can be changed with the
343 environment variable and augmented with the
345 environment variable, see mh\-profile(5).
348 Failure to open any mail transport configuration file is silently
349 ignored. Therefore, it's best to avoid dynamic creation of such
350 a file with the intent of use via the
354 environment variables. If such use is necessary, the ability
355 to successfully open the file should first be verified.