1 .TH MH-TAILOR %manext5% "July 11, 2012" "%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
61 For backward compatibility,
66 The third alternative,
68 also forks a local copy of
70 but feeds the message directly to it, using
73 This replaces the old, undocumented
75 mechanism and retains some of its limitations, such as lack of
79 \*(lqDcc:\*(rq header field.
86 considers local. It should typically be a fully
87 qualified hostname. If this is not set, depending on the version of
90 will query the system for this value
91 (e.g. uname, gethostname, etc.), and attempt to fully qualify this
94 If you are using POP to retrieve new messages, you may want to set this
95 value to the name of the POP server, so that outgoing message appear to
96 have originated on the POP server.
101 If this is set, a `.' followed by this string will be appended to your
104 This should only be needed, if for some reason
107 fully qualify the hostname returned by the system (e.g. uname,
113 This option specifies the host name that
120 command, when posting mail. If not
121 set, the default is to use the host name that
126 above). If this option is set, but empty, no
128 command will be given.
132 command is required by RFC\-821, many SMTP servers
133 do not require it. Early versions of
135 will fail if the hostname
138 command is the local host. Later versions of
140 will complain if you omit the
144 find out what your system expects and set this field if needed.
149 This option is only used for UUCP mail. It specifies the name of the
150 local host in the UUCP \*(lqdomain\*(rq. If not set, depending
151 on the version of UNIX you're running,
153 will query the system
154 for this value. This has no equivalent in the
163 The directory where maildrops are kept. If this option is set, but empty,
164 the user's home directory is used. This overrides the default value
165 chosen at the time of compilation.
170 The name of the maildrop file in the directory where maildrops are kept.
171 If this is empty, the user's login name is used. This overrides the default
172 value (which is empty).
176 \&\\001\\001\\001\\001\\n
178 The beginning-of-message delimiter for maildrops.
182 \&\\001\\001\\001\\001\\n
184 The end-of-message delimiter for maildrops.
188 %libdir%/maildelivery
190 The name of the system-wide default
201 The highest user-id which should NOT receive mail addressed to
207 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
208 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
209 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
210 This is useful for handling admin, dummy, and guest logins.
213 This option is only available if you set
221 A lists of hosts and networks which to look for SMTP servers when
222 posting non\-local mail. It turns out this is a major win for hosts
223 which don't run an message transport system. The value of
225 should be one or more items. Each item is the name of a host which
226 is (hopefully) running a SMTP server.
228 This option is only available if you set
240 .SS "Post Office Protocol"
241 This option is only available if you have compiled
243 with POP support enabled (i.e., \*(lq--enable-pop\*(rq).
247 The name of the default POP service host. If this is not set, then
249 looks in the standard maildrop areas for waiting mail, otherwise
250 the named POP service host is consulted.
252 \" .SS "BBoards Delivery"
253 \" This option is only available if you compiled \fInmh\fP with
254 \" \*(lqbbdelivery:\ on\*(rq.
258 \" The local BBoards domain (a UCI hack).
260 \" .SS "BBoards & The POP"
261 \" These options are only available if you compiled \fInmh\fP with
262 \" \*(lqbboards:\ pop\*(rq and \*(lqpop:\ on\*(rq.
266 \" The POP service host which also acts as a BBoard server. This variable
267 \" should be set on the POP BBoards client host.
272 \" The guest account on the POP/BB service host. This should be a different
273 \" login ID than either the POP user or the BBoards user. (The user-id
274 \" \*(lqftp\*(rq is highly recommended.) This variable should be set on
275 \" both the POP BBoards client and service hosts.
279 \" %etcdir%/hosts.popbb
281 \" A file containing of lists of hosts that are allowed to use the POP
282 \" facility to access BBoards using the guest account. If this file is not
283 \" present, then no check is made. This variable should be set on the POP
284 \" BBoards service host.
287 A few words on locking:
289 has several methods for creating locks
290 on files. When configuring
292 you will need to decide on the
293 locking style and locking directory (if any). The first controls the
294 method of locking, the second says where lock files should be created.
298 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
301 system call; use \*(lq--with-locking=lockf\*(rq if
304 system call; or use \*(lq--with-locking=fcntl\*(rq
305 if you want to use the
307 system call for kernel-level locking.
309 Instead of kernel locking, you can configure
311 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
313 a file should be created whose existence means \*(lqlocked\*(rq and
314 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
315 constructed by appending \*(lq.lock\*(rq to the name of the file being
316 locked. If \*(lq--enable-lockdir=directory\*(rq
317 is not specified at build time, lock files will be created
318 in the directory where the file being locked resides. Otherwise, lock
319 files will be created in the directory specified by
320 \*(lq--enable-lockdir\*(rq.
324 you should see how locking is done at
325 your site, and set the appropriate values.
329 .ta \w'%etcdir%/ExtraBigFileName 'u
330 ^%etcdir%/mts.conf~^nmh mts configuration file
332 .SH "PROFILE COMPONENTS"
338 As listed above. The path of the mail transport configuration
339 file can be changed with the
341 environment variable and augmented with the
343 environment variable, see mh\-profile(5).
345 Failure to open any mail transport configuration file is silently
346 ignored. Therefore, it's best to avoid dynamic creation of such
347 a file with the intent of use via the
351 environment variables. If such use is necessary, the ability
352 to successfully open the file should first be verified.
projects / mmh / blob