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:
31 will send messages by forking a
35 If you are using POP to retrieve new messages, you may want to set this
36 value to the name of the POP server, so that outgoing message appear to
37 have originated on the POP server.
40 This should only be needed, if for some reason
43 fully qualify the hostname returned by the system (e.g. uname,
50 The directory where maildrops are kept. If this option is set, but empty,
51 the user's home directory is used. This overrides the default value
52 chosen at the time of compilation.
57 The name of the maildrop file in the directory where maildrops are kept.
58 If this is empty, the user's login name is used. This overrides the default
59 value (which is empty).
63 \&\\001\\001\\001\\001\\n
65 The beginning-of-message delimiter for maildrops.
69 \&\\001\\001\\001\\001\\n
71 The end-of-message delimiter for maildrops.
76 This directive controls three different types of email address masquerading.
77 The three possible values, which may be specified in any combination on the
78 line, separated by spaces, are \*(lqdraft_from\*(rq, \*(lqmmailid\*(rq, and
79 \*(lqusername_extension\*(rq.
81 \*(lqmmailid\*(rq was the only type of masquerading in the original MH package, and
82 apparently stands for \*(lqmasquerade mail identification\*(rq. This type of
83 masquerading keys off of the GECOS field of the passwd file. When enabled,
85 will check if the user's pw_gecos field in the passwd file is of the
89 Full Name <fakeusername>
92 If it is, the internal
94 routines that find the username and full name
95 of that user will return \*(lqfakeusername\*(rq and \*(lqFull Name\*(rq respectively. This is
96 useful if you want the messages you send to always appear to come from the name
97 of an MTA alias rather than your actual account name. For instance, many
98 organizations set up \*(lqFirst.Last\*(rq sendmail aliases for all users. If this is
99 the case, the GECOS field for each user should look like:
102 First [Middle] Last <First.Last>
105 \*(lqusername_extension\*(rq, when specified on the \*(lqmasquerade:\*(rq line, allows a second
106 type of username masquerading. If the user sets the
107 .B $USERNAME_EXTENSION
108 environment variable, its value will be appended to the actual login name. For
109 instance, if I am \*(lqdan@company.com\*(rq, and I set
110 .B $USERNAME_EXTENSION
111 to \*(lq\-www\*(rq, my mail will appear to come from \*(lqdan\-www@company.com\*(rq. This is meant
112 to interact with qmail's \*(lquser\-extension\*(rq feature, where mail sent to
116 Likewise, those using
117 versions of sendmail for which \*(lqplussed user\*(rq processing is active can set
118 .B $USERNAME_EXTENSION
119 to \*(lq+\fIstring\fR\*(rq. These MTA features are useful
120 because they allow one to use different email addresses in different situations
121 (to aid in automatic mail filtering or in determining where spammers got one's
122 address) while only actually having a single account. Note that
123 .B $USERNAME_EXTENSION
124 is only appended to the username when \fIpost\fR is
125 generating \*(lq[Resent\-]From:\*(rq lines and the SMTP envelope
128 for instance, will not try to read from a maildrop file called \*(lqdan\-www\*(rq (to
129 recall the earlier example).
131 \*(lqdraft_from\*(rq controls the most powerful type of address masquerading. Normally,
132 when a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
135 rather than constructing its own. However, to discourage email forgery, the
136 SMTP envelope \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
137 When \*(lqdraft_from\*(rq is turned on, though, the envelope \*(lqFrom:\*(rq will use the
138 address specified in the draft, and there will be no \*(lqSender:\*(rq header. This is
139 useful when a user wants to pretend to be sending mail \*(lqdirectly\*(rq from a remote
140 POP3 account, or when remote mail robots incorrectly use the envelope \*(lqFrom:\*(rq in
141 preference to the body \*(lqFrom:\*(rq (or refuse to take action when the two don't
142 match). Note that the MTA may still reveal the user's real identity (e.g.
144 \*(lqX\-Authentication\-Warning:\*(rq header).
148 %libdir%/maildelivery
150 The name of the system-wide default
161 The highest user-id which should NOT receive mail addressed to
167 If set, then each user-id greater than \*(lqeveryone\*(rq that has a
168 login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
169 indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
170 This is useful for handling admin, dummy, and guest logins.
172 A few words on locking:
174 has several methods for creating locks
175 on files. When configuring
177 you will need to decide on the
178 locking style and locking directory (if any). The first controls the
179 method of locking, the second says where lock files should be created.
183 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
186 system call; use \*(lq--with-locking=lockf\*(rq if
189 system call; or use \*(lq--with-locking=fcntl\*(rq
190 if you want to use the
192 system call for kernel-level locking.
194 Instead of kernel locking, you can configure
196 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
198 a file should be created whose existence means \*(lqlocked\*(rq and
199 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
200 constructed by appending \*(lq.lock\*(rq to the name of the file being
203 is not specified, lock files will be created
204 in the directory where the file being locked resides. Otherwise, lock
205 files will be created in the directory specified by
210 you should see how locking is done at
211 your site, and set the appropriate values.
216 .ta \w'%etcdir%/ExtraBigFileName 'u
217 ^%etcdir%/mts.conf~^nmh mts configuration file
220 .SH "PROFILE COMPONENTS"