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 ]
43 is the default program called by
48 to local and remote users. In fact, most of
49 the features attributed to
51 in its manual page are performed by
55 acting as a relatively simple preprocessor.
58 which parses the various header fields, appends
59 \*(lqFrom:\*(rq and \*(lqDate:\*(rq lines, and interacts with the mail transport system.
61 will not normally be called directly by the user.
64 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
65 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
66 message for destination addresses, checks these addresses for validity,
67 and formats them so as to conform to ARPAnet Internet Message Format
70 flag is set. This will normally cause
71 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
72 address, as well as any local return addresses. The
75 switch can be used to indicate the preferred length of the header
76 components that contain addresses.
78 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
79 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
80 sent to sighted recipients. The blind recipients will receive an entirely
81 new message with a minimal set of headers. Included in the body of the
82 message will be a copy of the message sent to the sighted recipients.
86 is specified, then this copy is filtered
89 prior to being sent to the blind recipients.
95 the MIME rules for encapsulation.
100 switch can be used to specify a file that post
101 should take aliases from. More than one file can be specified, each
104 In any event, the primary alias file is
109 switch indicates that a \*(lqMessage\-ID:\*(rq or
110 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
114 switch indicates that the user should be informed of
115 each step of the posting/filing process.
119 switch indicates that the user would like to watch the
120 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
123 Under normal circumstances,
125 constructs the \*(lqFrom:\*(rq line of the
126 message from the user's login name, the full name from the GECOS field of the
127 passwd file, and the fully\-qualified name of the local machine (or the
129 \*(lqlocalname\*(rq in
131 if set). An example is \*(lqFrom: Dan Harkless
132 <dan@machine.example.com>\*(rq. There are four ways to override these values,
133 however. Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
137 The first way is GECOS\-based username masquerading. If the \*(lqmasquerade:\*(rq line
140 contains \*(lqmmailid\*(rq, this processing is activated. If a user's GECOS
141 field in the passwd file is of the form \*(lqFull Name <fakename>\*(rq then \*(lqfakename\*(rq
142 will be used in place of the real username. For instance, a GECOS field of \*(lqDan
143 Harkless <Dan.Harkless>\*(rq would result in \*(lqFrom: Dan Harkless
144 <Dan.Harkless@machine.example.com>\*(rq. Naturally if you were doing something like
145 this you'd want to set up an MTA alias (e.g. in /etc/aliases) from, for
146 instance, \*(lqDan.Harkless\*(rq to \*(lqdan\*(rq.
148 The second way to override default construction of \*(lqFrom:\*(rq is to set the
150 environment variable. This variable overrides the full name
151 from the GECOS field, even if GECOS\-based masquerading is being done. This
152 processing is always active, and does not need to be enabled from
155 The third way is controlled by the \*(lquser_extension\*(rq value of \*(lqmasquerade:\*(rq line
158 When that's turned on, setting the
159 .B $USERNAME_EXTENSION
160 environment variable will result in its value being appended the user's login
161 name. For instance, if I set
162 .B $USERNAME_EXTENSION
163 to \*(lq+www\*(rq, my \*(lqFrom:\*(rq
164 line will contain \*(lqDan Harkless <dan+www@machine.example.com>\*(rq (or
165 \*(lqDan.Harkless+www\*(rq if I'm using mmailid masquerading as well). Recent versions
168 automatically deliver all mail sent to
173 has a similar feature which uses '\-' as the delimiter by
174 default, but can use other characters as well.
176 The fourth method of address masquerading is to specify a \*(lqFrom:\*(rq line manually
177 in the message draft. It will be used as provided (after alias substitution),
178 but normally, to discourage email forgery, the user's
181 used in the SMTP envelope \*(lqFrom:\*(rq and in a \*(lqSender:\*(rq header. However, if the
182 \*(lqmasquerade:\*(rq line of
184 contains \*(lqdraft_from\*(rq, the SMTP envelope \*(lqFrom:\*(rq
185 will use the address given in the draft \*(lqFrom:\*(rq, and there will be no \*(lqSender:\*(rq
186 header. This is useful in pretending to send mail \*(lqdirectly\*(rq from a remote POP3
187 account, or when remote email robots give improper precedence to the envelope
188 \*(lqFrom:\*(rq. Note that your MTA may still reveal your real identity (e.g.
190 \*(lqX\-Authentication\-Warning:\*(rq header).
192 If nmh is using the SMTP MTA, the
196 switches can be used to override the default mail server (defined by the
204 has been compiled with SASL support, the
208 switches will enable and disable
209 the use of SASL authentication with the SMTP MTA. Depending on the
210 SASL mechanism used, this may require an additional password prompt from the
212 .RI \*(lq \&.netrc \*(rq
213 file can be used to store this password).
215 switch can be used to select a particular SASL mechanism,
218 switch can be used to select a authorization userid
219 to provide to SASL other than the default.
221 If SASL authentication is successful,
223 will attempt to negotiate a security layer for session encryption.
224 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
225 viewing the SMTP transaction with the
229 switch can be used to select the maximum value of the Security Strength Factor.
230 This is an integer value and the exact meaning of this value depends on the
231 underlying SASL mechanism. A value of 0 disables encryption.
235 has been compiled with TLS support, the
239 switches will require and disable the negotiation of TLS support when
241 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
242 `(tls-decrypted)' when viewing the SMTP transction with the
249 .ta \w'%etcdir%/ExtraBigFileName 'u
250 ^%etcdir%/mts.conf~^nmh mts configuration file
251 ^%etcdir%/MailAliases~^global nmh alias file
252 ^%bindir%/refile~^Program to process Fcc:s
253 ^%libdir%/mhl~^Program to process Bcc:s
256 .SH "PROFILE COMPONENTS"
264 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
265 .I "Standard for the Format of ARPA Internet Text Messages"
270 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
276 .RB ` "\-width\ 72" '
284 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
285 to the 822 specification, but
287 won't let you use them.