4 .TH POST %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
6 post \- deliver a message
16 .RB [ \-format " | " \-noformat ]
17 .RB [ \-mime " | " \-nomime ]
18 .RB [ \-msgid " | " \-nomsgid ]
19 .RB [ \-verbose " | " \-noverbose ]
20 .RB [ \-watch " | " \-nowatch ]
34 is the default program called by
39 to local and remote users. In fact, most of
40 the features attributed to
42 in its manual page are performed by
46 acting as a relatively simple preprocessor.
49 which parses the various header fields, appends
50 \*(lqFrom:\*(rq and \*(lqDate:\*(rq lines, and interacts with the mail transport system.
52 will not normally be called directly by the user.
55 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
56 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
57 message for destination addresses, checks these addresses for validity,
58 and formats them so as to conform to ARPAnet Internet Message Format
61 flag is set. This will normally cause
62 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
63 address, as well as any local return addresses. The
66 switch can be used to indicate the preferred length of the header
67 components that contain addresses.
69 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
70 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
71 sent to sighted recipients. The blind recipients will receive an entirely
72 new message with a minimal set of headers. Included in the body of the
73 message will be a copy of the message sent to the sighted recipients.
77 is specified, then this copy is filtered
80 prior to being sent to the blind recipients.
86 the MIME rules for encapsulation.
91 switch can be used to specify a file that post
92 should take aliases from. More than one file can be specified, each
95 In any event, the primary alias file is
100 switch indicates that a \*(lqMessage\-ID:\*(rq or
101 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
105 switch indicates that the user should be informed of
106 each step of the posting/filing process.
110 switch indicates that the user would like to watch the
111 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
114 Under normal circumstances,
116 constructs the \*(lqFrom:\*(rq line of the
117 message from the user's login name, the full name from the GECOS field of the
118 passwd file, and the fully\-qualified name of the local machine (or the
120 \*(lqlocalname\*(rq in
122 if set). An example is \*(lqFrom: Dan Harkless
123 <dan@machine.company.com>\*(rq. There are four ways to override these values,
124 however. Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
128 The first way is GECOS\-based username masquerading. If the \*(lqmasquerade:\*(rq line
131 contains \*(lqmmailid\*(rq, this processing is activated. If a user's GECOS
132 field in the passwd file is of the form \*(lqFull Name <fakename>\*(rq then \*(lqfakename\*(rq
133 will be used in place of the real username. For instance, a GECOS field of \*(lqDan
134 Harkless <Dan.Harkless>\*(rq would result in \*(lqFrom: Dan Harkless
135 <Dan.Harkless@machine.company.com>\*(rq. Naturally if you were doing something like
136 this you'd want to set up an MTA alias (e.g. in /etc/aliases) from, for
137 instance, \*(lqDan.Harkless\*(rq to \*(lqdan\*(rq.
139 The second way to override default construction of \*(lqFrom:\*(rq is to set the
141 environment variable. This variable overrides the full name
142 from the GECOS field, even if GECOS\-based masquerading is being done. This
143 processing is always active, and does not need to be enabled from
146 The third way is controlled by the \*(lquser_extension\*(rq value of \*(lqmasquerade:\*(rq line
149 When that's turned on, setting the
150 .B $USERNAME_EXTENSION
151 environment variable will result in its value being appended the user's login
152 name. For instance, if I set
153 .B $USERNAME_EXTENSION
154 to \*(lq+www\*(rq, my \*(lqFrom:\*(rq
155 line will contain \*(lqDan Harkless <dan+www@machine.company.com>\*(rq (or
156 \*(lqDan.Harkless+www\*(rq if I'm using mmailid masquerading as well). Recent versions
159 automatically deliver all mail sent to
164 has a similar feature which uses '\-' as the delimiter by
165 default, but can use other characters as well.
167 The fourth method of address masquerading is to specify a \*(lqFrom:\*(rq line manually
168 in the message draft. It will be used as provided (after alias substitution),
169 but normally, to discourage email forgery, the user's
172 used in the SMTP envelope \*(lqFrom:\*(rq and in a \*(lqSender:\*(rq header. However, if the
173 \*(lqmasquerade:\*(rq line of
175 contains \*(lqdraft_from\*(rq, the SMTP envelope \*(lqFrom:\*(rq
176 will use the address given in the draft \*(lqFrom:\*(rq, and there will be no \*(lqSender:\*(rq
177 header. This is useful in pretending to send mail \*(lqdirectly\*(rq from a remote POP3
178 account, or when remote email robots give improper precedence to the envelope
179 \*(lqFrom:\*(rq. Note that your MTA may still reveal your real identity (e.g.
181 \*(lqX\-Authentication\-Warning:\*(rq header).
183 If nmh is using the SMTP MTA, the
187 switches can be used to override the default mail server (defined by the
195 has been compiled with SASL support, the
198 the use of SASL authentication with the SMTP MTA. Depending on the
199 SASL mechanism used, this may require an additional password prompt from the
201 .RI \*(lq \&.netrc \*(rq
202 file can be used to store this password).
204 switch can be used to select a particular SASL mechanism,
207 switch can be used to select a authorization userid
208 to provide to SASL other than the default.
210 If SASL authentication is successful,
212 will attempt to negotiate a security layer for session encryption.
213 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
214 viewing the SMTP transaction with the
220 has been compiled with TLS support, the
222 switch will require the negotiation of TLS support when connecting to the
223 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
224 `(tls-decrypted)' when viewing the SMTP transction with the
231 .ta \w'%etcdir%/ExtraBigFileName 'u
232 ^%etcdir%/mts.conf~^nmh mts configuration file
233 ^%etcdir%/MailAliases~^global nmh alias file
234 ^%bindir%/refile~^Program to process Fcc:s
235 ^%libdir%/mhl~^Program to process Bcc:s
238 .SH "PROFILE COMPONENTS"
246 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
247 .I "Standard for the Format of ARPA Internet Text Messages"
252 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
258 .RB ` "\-width\ 72" '
266 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
267 to the 822 specification, but
269 won't let you use them.