5 .\" include the -mh macro file
8 .TH MH-TAILOR %manext5% MH.6.8 [%nmhversion%]
10 mh-tailor, mts.conf \- mail transport customization for nmh message handler
15 \fI%etcdir%/mts.conf\fP
18 The file %etcdir%/mts.conf defines run-time options for those \fInmh\fR
19 programs which interact (in some form) with the message transport system.
20 At present, these (user) programs are: \fIap\fR, \fIconflict\fR,
21 \fIinc\fR, \fImsgchk\fR, \fImsh\fR, \fIpost\fR, \fIrcvdist\fR, and
24 Each option should be given on a single line. Blank lines and lines
25 which begin with `#' are ignored. The options available along with
26 default values and a description of their meanings are listed below:
32 The hostname \fInmh\fR considers local. It should typically be a fully
33 qualified hostname. If this is not set, depending on the version of
34 UNIX you're running, \fInmh\fR will query the system for this value
35 (e.g., uname, gethostname, etc.), and attempt to fully qualify this
38 If you are using POP to retrieve new messages, you may want to set this
39 value to the name of the POP server, so that outgoing message appear to
40 have originated on the POP server.
45 If this is set, a `.' followed by this string will be appended to your
48 This should only be needed, if for some reason \fInmh\fR is not able to
49 fully qualify the hostname returned by the system (e.g., uname,
55 This option specifies the host name that \fInmh\fP will give in the
56 SMTP \fBHELO\fP (and \fBEHLO\fP) command, when posting mail. If not
57 set, the default is to use the host name that \fInmh\fR considers local
58 (see \*(lqlocalname\*(rq above). If this option is set, but empty, no
59 \fBHELO\fP command will be given.
62 Although the \fBHELO\fP command is required by RFC\-821, many SMTP servers
63 do not require it. Early versions of SendMail will fail if the hostname
64 given in the \fBHELO\fP command is the local host. Later versions of
65 SendMail will complain if you omit the \fBHELO\fP command. If you run
66 SendMail, find out what your system expects and set this field if needed.
71 This option is only used for UUCP mail. It specifies the name of the
72 local host in the \fIUUCP\fR \*(lqdomain\*(rq. If not set, depending
73 on the version of UNIX you're running, \fInmh\fR will query the system
74 for this value. This has no equivalent in the \fInmh\fR configuration
80 The directory where maildrops are kept. If this option is set, but empty,
81 the user's home directory is used. This overrides the default value
82 chosen at the time of compilation.
87 The name of the maildrop file in the directory where maildrops are kept.
88 If this is empty, the user's login name is used. This overrides the default
89 value (which is empty).
92 mmdelim1: \\001\\001\\001\\001\\n
94 The beginning-of-message delimiter for maildrops.
97 mmdelim2: \\001\\001\\001\\001\\n
99 The end-of-message delimiter for maildrops.
104 If this is non-zero, then activate support for MMailids (username
105 masquerading). When this is activated, \fInmh\fR will check if the
106 pw_gecos field in the password file has the form
109 Full Name <fakeusername>
111 If the pw_gecos field has this form, then the internal \fInmh\fR
112 routines that find the username and full name of a user will return
113 \*(lqfakeusername\*(rq and \*(lqFull Name\*(rq respectively. If
114 the pw_gecos field for a user is not of this form, there will be
115 no username masquerading for that user.
117 This facility is useful if you are using POP, and wish for messages
118 that are sent by users to appear to originate from the username of
119 their POP account, rather than their username on the local machine.
122 maildelivery: %libdir%/maildelivery
124 The name of the system-wide default \fI\&.maildelivery\fR file.
125 See \fIslocal\fR\0(1) for the details.
130 The highest user-id which should NOT receive mail addressed to
136 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
137 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
138 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
139 This is useful for handling admin, dummy, and guest logins.
143 These options are only available if you compiled \fInmh\fP with the
144 \*(lq/smtp\*(rq support.
148 hostable: %etcdir%/hosts
150 The exceptions file for /etc/hosts used by \fIpost\fR to try to find
151 official names. The format of this file is quite simple:
154 1. Comments are surrounded by sharp (`#') and newline.
156 2. Words are surrounded by white space.
158 3. The first word on the line is the official name of a host.
160 4. All words following the official names are aliases for that host.
164 servers: localhost \\01localnet
166 A lists of hosts and networks which to look for SMTP servers when
167 posting local mail. It turns out this is a major win for hosts which
168 don't run an message transport system. The value of \*(lqservers\*(rq
169 should be one or more items. Each item is the name of either a host
170 or a net (in the latter case, precede the name of the net by a \\01).
171 This list is searched when looking for a smtp server to post mail.
172 If a host is present, the SMTP port on that host is tried. If a net
173 is present, the SMTP port on each host in that net is tried. Note that
174 if you are running with the BIND code, then any networks specified are
175 ignored (sorry, the interface went away under BIND).
179 This option is only available if you compiled \fInmh\fP to use
180 \fISendMail\fP as your delivery agent.
184 sendmail: %sendmailpath%
186 The pathname to the \fIsendmail\fR program.
189 .Uh "Post Office Protocol"
190 This option is only available if you have compiled \fInmh\fP with POP
191 support enabled (i.e., \*(lq--enable-nmh-pop\*(rq).
197 The name of the default POP service host. If this is not set, then
198 \fInmh\fR looks in the standard maildrop areas for waiting mail, otherwise
199 the named POP service host is consulted.
202 .Uh "BBoards Delivery"
203 This option is only available if you compiled \fInmh\fP with
204 \*(lqbbdelivery:\ on\*(rq.
210 The local BBoards domain (a UCI hack).
213 .Uh "BBoards & The POP"
214 These options are only available if you compiled \fInmh\fP with
215 \*(lqbboards:\ pop\*(rq and \*(lqpop:\ on\*(rq.
221 The POP service host which also acts as a BBoard server. This variable
222 should be set on the POP BBoards client host.
227 The guest account on the POP/BB service host. This should be a different
228 login ID than either the POP user or the BBoards user. (The user-id
229 \*(lqftp\*(rq is highly recommended.) This variable should be set on
230 both the POP BBoards client and service hosts.
233 popbblist: %etcdir%/hosts.popbb
235 A file containing of lists of hosts that are allowed to use the POP
236 facility to access BBoards using the guest account. If this file is not
237 present, then no check is made. This variable should be set on the POP
238 BBoards service host.
242 .Uh "BBoards & The NNTP"
243 This option is only available if you compiled \fInmh\fP with
244 \*(lqbboards:\ nntp\*(rq and \*(lqpop:\ on\*(rq.
250 The host which provides the NNTP service. This variable should be set
251 on the NNTP BBoards client host.
255 A few words on locking: \fInmh\fR has several methods for creating locks
256 on files. When configuring \fInmh\fR, you will need to decide on the
257 locking style and locking directory (if any). The first controls the
258 method of locking, the second says where lock files should be created.
260 To configure \fInmh\fR for kernel locking, define \fBFLOCK_LOCKING\fP if
261 you want to use the \fIflock\fP system call; define \fBLOCKF_LOCKING\fP if
262 you want to use the \fIlockf\fP system call; or define \fBFCNTL_LOCKING\fP
263 if you want to use the \fIfcntl\fP system call for kernel-level locking.
265 Instead of kernel locking, you can configure \fInmh\fR to use dot
266 locking by defining \fBDOT_LOCKING\fP. Dot locking specifies that
267 a file should be created whose existence means \*(lqlocked\*(rq and
268 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
269 constructed by appending \*(lq.lock\*(rq to the name of the file being
270 locked. If \fBLOCKDIR\fP is not specified, lock files will be created
271 in the directory where the file being locked resides. Otherwise, lock
272 files will be created in the directory specified by \fBLOCKDIR\fP.
274 Prior to installing \fInmh\fR, you should see how locking is done at
275 your site, and set the appropriate values.
278 ^%etcdir%/mts.conf~^nmh mts configuration file
projects / mmh / blob