1MH-TAILOR(5)                  File Formats Manual                 MH-TAILOR(5)
2
3
4

NAME

6       mh-tailor, mts.conf - mail transport configuration for nmh message han‐
7       dler
8

DESCRIPTION

10       The file /etc/nmh/mts.conf defines run-time options for those nmh  pro‐
11       grams  which interact (in some form) with the message transport system.
12       At present, these (user) programs are: ap, inc, msgchk, post,  rcvdist,
13       and rcvpack.
14
15       Each  option  should  be given on a single line.  Blank lines and lines
16       which begin with `#' are ignored.  The  options  available  along  with
17       default values and a description of their meanings are listed below:
18
19       mts:
20            The  mail  transport  method to use.  The three acceptable options
21            are smtp (which is the default), sendmail/smtp, and sendmail/pipe.
22
23            If you use smtp, this will enable a direct SMTP interface in  nmh.
24            When  sending  mail,  instead  of  passing the message to the mail
25            transport agent, post will open a socket connection  to  the  mail
26            port on the machine specified in the servers entry.
27
28            If  you use sendmail/smtp, then post will send messages by forking
29            a local copy of sendmail.  It will  still  speak  SMTP  with  this
30            local copy of sendmail.  For backward compatibility, sendmail/smtp
31            can be abbreviated to sendmail.
32
33            The third alternative, sendmail/pipe, also forks a local  copy  of
34            sendmail  but feeds the message directly to it, using sendmail -t.
35            This replaces the old, undocumented spost  mechanism  and  retains
36            some  of  its  limitations,  such as lack of support for the -whom
37            switch and “Dcc:” header field.
38
39       localname:
40            The hostname nmh considers local.  It should typically be a  fully
41            qualified  hostname.  If this is not set, depending on the version
42            of Unix you're running, nmh will query the system for  this  value
43            (e.g. uname, gethostname, etc.), and attempt to fully qualify this
44            value.
45
46            If you are using POP to retrieve new messages, you may want to set
47            this  value  to  the name of the POP server, so that outgoing mes‐
48            sages appear to have originated on the POP server.
49
50       localdomain:
51            If this is set, a `.' followed by this string will be appended  to
52            your hostname.
53
54            This  should only be needed, if for some reason nmh is not able to
55            fully qualify the hostname returned by  the  system  (e.g.  uname,
56            gethostname, etc.).
57
58       clientname:
59            This option specifies the host name that nmh will give in the SMTP
60            HELO (and EHLO) command, when  posting  mail.   If  not  set,  the
61            default  is  to  use  the  host name that nmh considers local (see
62            localname above).  If this option is set, but empty, no HELO  com‐
63            mand will be given.
64
65            Although  the  HELO  command  is  required  by  RFC 821, many SMTP
66            servers do not require it.  Early versions of SendMail  will  fail
67            if  the  hostname  given  in  the  HELO command is the local host.
68            Later versions of SendMail will complain if you omit the HELO com‐
69            mand.   If you run SendMail, find out what your system expects and
70            set this field if needed.
71
72       systemname:
73            This option is only used for UUCP mail.  It specifies the name  of
74            the local host in the UUCP “domain”.  If not set, depending on the
75            version of Unix you're running, nmh will query the system for this
76            value.  This has no equivalent in the nmh configuration file.
77
78       mmdfldir: /var/mail
79            The  directory  where mail drops are kept.  If this option is set,
80            but empty, the user's home directory is used.  This overrides  the
81            default value chosen at the time of compilation.
82
83       mmdflfil:
84            The  name  of the mail drop file in the directory where mail drops
85            are kept.  If this is empty, the user's login name is used.   This
86            overrides the default value (which is empty).
87
88       spoollocking: fcntl
89            The  locking  algorithm to use when opening the mail drop.  Can be
90            any one of the following:
91
92                 fcntl dot flock lockf
93
94       maildelivery: /usr/libexec/nmh/maildelivery
95            The name of the system-wide default maildelivery file.   See  slo‐
96            cal(1) for the details.
97
98   SMTP support
99       This option is only available if you set mts to smtp.
100
101       servers: localhost
102            A  single  hostname to be used when performing mail submission via
103            SMTP.  Previous versions of nmh supported multiple  hostnames  for
104            servers,  but  the  current  version of nmh only supports a single
105            entry (the name is  kept  for  backwards  compatibility  reasons).
106            This  can  be overridden via the -server switch to send(1).  It is
107            not possible to change the mail  submission  port  number  in  the
108            servers  entry; see the -port switch to send(1) for this function‐
109            ality.
110
111   SendMail
112       This option is only available if you set mts to sendmail.
113
114       sendmail: /usr/sbin/sendmail
115            The pathname to the sendmail program.
116
117   Post Office Protocol
118       pophost:
119            The name of the default POP service host.  If  this  is  not  set,
120            then  nmh  looks in the standard mail drop areas for waiting mail,
121            otherwise the named POP service host is consulted.
122
123   File Locking
124       A few words on locking: nmh has two main uses for locking: locking  the
125       mail  spool  during  mail  incorporation,  and  locking  metadata files
126       (sequence files, the context) during updates.   These  locking  methods
127       can be configured separately from each other.
128
129       For locking the mail spool, the spoollocking entry in mh-tailor(5) will
130       control the locking algorithm to use when inc  incorporates  mail  from
131       the spool file.  If no entry is given, a default based on the operating
132       system type will be chosen.
133
134       For locking all other files, the  datalocking  entry  in  mh-profile(5)
135       controls  the  locking algorithm used for all other file access.  If no
136       entry is given, the fcntl lock method will be chosen.
137
138       If you do not wish to use  kernel-based  locking,  dot  locking  is  an
139       option  available.  If “--enable-lockdir=directory” is not specified at
140       build time, lock files will be created in the directory where the  file
141       being  locked  resides.   Otherwise,  lock files will be created in the
142       directory specified by “--enable-lockdir”.
143
144       Prior to installing nmh, you should see how locking  is  done  at  your
145       site, and set the appropriate values.
146

FILES

148       /etc/nmh/mts.conf   nmh mts configuration file
149

PROFILE COMPONENTS

151       None
152

SEE ALSO

154       mh-mts(8), post(8)
155

DEFAULTS

157       As listed above.  The path of the mail transport configuration file can
158       be changed with the MHMTSCONF environment variable and  augmented  with
159       the MHMTSUSERCONF environment variable, see mh-profile(5).
160

BUGS

162       Failure  to  open  any  mail  transport  configuration file is silently
163       ignored.  Therefore, it's best to avoid dynamic creation of such a file
164       with  the  intent of use via the MHMTSCONF or MHMTSUSERCONF environment
165       variables.  If such use is necessary, the ability to successfully  open
166       the file should first be verified.
167
168
169
170nmh-1.7.1                         2017-02-19                      MH-TAILOR(5)
Impressum