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:
25 Each option should be given on a single line. Blank lines and lines
26 which begin with `#' are ignored. The options available along with
27 default values and a description of their meanings are listed below:
30 will send messages by forking a
36 This directive controls email address masquerading.
37 The possible value is \*(lqusername_extension\*(rq.
39 If specified and if the user sets the
40 .B $USERNAME_EXTENSION
41 environment variable, its value will be appended to the actual login name. For
42 instance, if I am \*(lqdan@company.com\*(rq, and I set
43 .B $USERNAME_EXTENSION
44 to \*(lq\-www\*(rq, my mail will appear to come from \*(lqdan\-www@company.com\*(rq. This is meant
45 to interact with qmail's \*(lquser\-extension\*(rq feature, where mail sent to
50 versions of sendmail for which \*(lqplussed user\*(rq processing is active can set
51 .B $USERNAME_EXTENSION
52 to \*(lq+\fIstring\fR\*(rq. These MTA features are useful
53 because they allow one to use different email addresses in different situations
54 (to aid in automatic mail filtering or in determining where spammers got one's
55 address) while only actually having a single account. Note that
56 .B $USERNAME_EXTENSION
57 is only appended to the username when \fIpost\fR is
58 generating \*(lq[Resent\-]From:\*(rq lines and the SMTP envelope
61 for instance, will not try to read from a maildrop file called \*(lqdan\-www\*(rq (to
62 recall the earlier example).
65 When a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
68 rather than constructing its own. However, to discourage email forgery, the
69 SMTP envelope \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
75 The name of the system-wide default
82 A few words on locking:
84 has several methods for creating locks
85 on files. When configuring
87 you will need to decide on the
88 locking style and locking directory (if any). The first controls the
89 method of locking, the second says where lock files should be created.
93 for kernel locking, use the \*(lq--with-locking=flock\*(rq configure option if
96 system call; use \*(lq--with-locking=lockf\*(rq if
99 system call; or use \*(lq--with-locking=fcntl\*(rq
100 if you want to use the
102 system call for kernel-level locking.
104 Instead of kernel locking, you can configure
106 to use dot locking by using \*(lq--with-locking=dot\*(rq. Dot locking
108 a file should be created whose existence means \*(lqlocked\*(rq and
109 whose non-existence means \*(lqunlocked\*(rq. The name of this file is
110 constructed by appending \*(lq.lock\*(rq to the name of the file being
113 is not specified, lock files will be created
114 in the directory where the file being locked resides. Otherwise, lock
115 files will be created in the directory specified by
120 you should see how locking is done at
121 your site, and set the appropriate values.
126 .ta \w'%etcdir%/ExtraBigFileName 'u
127 ^%etcdir%/mts.conf~^nmh mts configuration file
130 .SH "PROFILE COMPONENTS"