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 ]
35 is the default program called by
40 to local and remote users. In fact, most of
41 the features attributed to
43 in its manual page are performed by
47 acting as a relatively simple preprocessor.
50 which parses the various header fields, appends
51 \*(lqFrom:\*(rq and \*(lqDate:\*(rq lines, and interacts with the mail transport system.
53 will not normally be called directly by the user.
56 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
57 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
58 message for destination addresses, checks these addresses for validity,
59 and formats them so as to conform to ARPAnet Internet Message Format
62 flag is set. This will normally cause
63 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
64 address, as well as any local return addresses. The
67 switch can be used to indicate the preferred length of the header
68 components that contain addresses.
70 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
71 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
72 sent to sighted recipients. The blind recipients will receive an entirely
73 new message with a minimal set of headers. Included in the body of the
74 message will be a copy of the message sent to the sighted recipients.
78 is specified, then this copy is filtered
81 prior to being sent to the blind recipients.
87 the MIME rules for encapsulation.
92 switch can be used to specify a file that post
93 should take aliases from. More than one file can be specified, each
96 In any event, the primary alias file is
101 switch indicates that a \*(lqMessage\-ID:\*(rq or
102 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
106 switch indicates that the user should be informed of
107 each step of the posting/filing process.
111 switch indicates that the user would like to watch the
112 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
115 Under normal circumstances,
117 constructs the \*(lqFrom:\*(rq line of the
118 message from the user's login name, the full name from the GECOS field of the
119 passwd file, and the fully\-qualified name of the local machine (or the
121 \*(lqlocalname\*(rq in
123 if set). An example is \*(lqFrom: Dan Harkless
124 <dan@machine.company.com>\*(rq. There are four ways to override these values,
125 however. Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
129 The first way is GECOS\-based username masquerading. If the \*(lqmasquerade:\*(rq line
132 contains \*(lqmmailid\*(rq, this processing is activated. If a user's GECOS
133 field in the passwd file is of the form \*(lqFull Name <fakename>\*(rq then \*(lqfakename\*(rq
134 will be used in place of the real username. For instance, a GECOS field of \*(lqDan
135 Harkless <Dan.Harkless>\*(rq would result in \*(lqFrom: Dan Harkless
136 <Dan.Harkless@machine.company.com>\*(rq. Naturally if you were doing something like
137 this you'd want to set up an MTA alias (e.g. in /etc/aliases) from, for
138 instance, \*(lqDan.Harkless\*(rq to \*(lqdan\*(rq.
140 The second way to override default construction of \*(lqFrom:\*(rq is to set the
142 environment variable. This variable overrides the full name
143 from the GECOS field, even if GECOS\-based masquerading is being done. This
144 processing is always active, and does not need to be enabled from
147 The third way is controlled by the \*(lquser_extension\*(rq value of \*(lqmasquerade:\*(rq line
150 When that's turned on, setting the
151 .B $USERNAME_EXTENSION
152 environment variable will result in its value being appended the user's login
153 name. For instance, if I set
154 .B $USERNAME_EXTENSION
155 to \*(lq+www\*(rq, my \*(lqFrom:\*(rq
156 line will contain \*(lqDan Harkless <dan+www@machine.company.com>\*(rq (or
157 \*(lqDan.Harkless+www\*(rq if I'm using mmailid masquerading as well). Recent versions
160 automatically deliver all mail sent to
165 has a similar feature which uses '\-' as the delimiter by
166 default, but can use other characters as well.
168 The fourth method of address masquerading is to specify a \*(lqFrom:\*(rq line manually
169 in the message draft. It will be used as provided (after alias substitution),
170 but normally, to discourage email forgery, the user's
173 used in the SMTP envelope \*(lqFrom:\*(rq and in a \*(lqSender:\*(rq header. However, if the
174 \*(lqmasquerade:\*(rq line of
176 contains \*(lqdraft_from\*(rq, the SMTP envelope \*(lqFrom:\*(rq
177 will use the address given in the draft \*(lqFrom:\*(rq, and there will be no \*(lqSender:\*(rq
178 header. This is useful in pretending to send mail \*(lqdirectly\*(rq from a remote POP3
179 account, or when remote email robots give improper precedence to the envelope
180 \*(lqFrom:\*(rq. Note that your MTA may still reveal your real identity (e.g.
182 \*(lqX\-Authentication\-Warning:\*(rq header).
184 If nmh is using the SMTP MTA, the
188 switches can be used to override the default mail server (defined by the
196 has been compiled with SASL support, the
199 the use of SASL authentication with the SMTP MTA. Depending on the
200 SASL mechanism used, this may require an additional password prompt from the
202 .RI \*(lq \&.netrc \*(rq
203 file can be used to store this password).
205 switch can be used to select a particular SASL mechanism,
208 switch can be used to select a authorization userid
209 to provide to SASL other than the default.
211 If SASL authentication is successful,
213 will attempt to negotiate a security layer for session encryption.
214 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
215 viewing the SMTP transaction with the
221 has been compiled with TLS support, the
223 switch will require the negotiation of TLS support when connecting to the
224 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
225 `(tls-decrypted)' when viewing the SMTP transction with the
232 .ta \w'%etcdir%/ExtraBigFileName 'u
233 ^%etcdir%/mts.conf~^nmh mts configuration file
234 ^%etcdir%/MailAliases~^global nmh alias file
235 ^%bindir%/refile~^Program to process Fcc:s
236 ^%libdir%/mhl~^Program to process Bcc:s
239 .SH "PROFILE COMPONENTS"
247 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
248 .I "Standard for the Format of ARPA Internet Text Messages"
253 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
259 .RB ` "\-width\ 72" '
267 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
268 to the 822 specification, but
270 won't let you use them.