5 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
19 .RB [ \-nodraftfolder ]
23 .RB [ \-format " | " \-noformat ]
24 .RB [ \-forward " | " \-noforward ]
25 .RB [ \-mime " | " \-nomime ]
26 .RB [ \-msgid " | " \-nomsgid ]
27 .RB [ \-push " | " \-nopush ]
30 .RB [ \-verbose " | " \-noverbose ]
31 .RB [ \-watch " | " \-nowatch ]
44 .IR header-field-name ]
48 will cause each of the specified files to be delivered
49 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
50 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
52 is re\-distributing a message, as invoked from
55 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
62 delivery of the messages, although this can be changed by defining the
64 profile component. Most of the features attributed to
66 are actually performed by
74 option, the draft is scanned for a header whose field name matches the
76 .IR header-field-name .
77 The draft is converted to a MIME message if one or more matches are found.
78 This conversion occurs before all other processing.
80 The first part of the MIME message is the draft body if that body contains
81 any non-blank characters.
82 The body of each header field whose name matches the
84 is interpreted as a file name, and each file named is included as a separate
85 part in the MIME message.
87 For file names with dot suffixes, the context is scanned for a
89 entry for that suffix.
90 The content-type for the part is taken from that context entry if a match is
92 If no match is found or the file does not have a dot suffix, the content-type
93 is text/plain if the file contains only ASCII characters or application/octet-stream
94 if it contains characters outside of the ASCII range.
96 Each part contains a name attribute that is the last component of the path name.
99 attribute containing the file mode accompanies each part.
100 Finally, a description attribute is generated by running the
108 will detach itself from the user's
109 terminal and perform its actions in the background. If
111 and the draft can't be sent, then an error message will be sent (using
112 the mailproc) back to the user. If
114 is given, then a copy
115 of the draft will be attached to this failure notice. Using
119 in the background because the output is
120 trapped and analyzed by
127 will indicate the interactions
128 occurring with the transport system, prior to actual delivery.
133 will monitor the delivery of local
134 and network mail. Hence, by specifying both switches, a large detail
135 of information can be gathered about each step of the message's entry
136 into the transport system.
147 draft folder facility. This is an advanced (and highly
148 useful) feature. Consult the
157 will split the draft into one
158 or more partial messages prior to sending. This makes use of the
166 then this switch is ignored\0--\0it makes
167 no sense to redistribute a message in this fashion. Sometimes you want
169 to pause after posting a partial message. This is usually
170 the case when you are running
172 and expect to generate a
173 lot of partial messages. The argument to
176 to pause between postings.
181 argument will query whether the draft
182 is the intended file, whereas
184 will suppress this question.
185 Once the transport system has successfully accepted custody of the
186 message, the file will be renamed with a leading comma, which allows
187 it to be retrieved until the next draft message is sent. If there are
188 errors in the formatting of the message,
191 (hopefully) helpful error message.
193 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
194 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
195 sent to sighted recipients. The blind recipients will receive an entirely
196 new message with a minimal set of headers. Included in the body of the
197 message will be a copy of the message sent to the sighted recipients.
199 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
200 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
201 blind recipients will receive the same message sent to the sighted
202 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
203 explicit indication that they have received a \*(lqblind copy\*(rq.
204 This can cause blind recipients to
205 inadvertently reply to all of the sighted recipients of the
206 original message, revealing that they received a blind copy.
207 On the other hand, since a normal reply to a message sent
208 via a \*(lqBcc:\*(rq field
209 will generate a reply only to the sender of the original message,
210 it takes extra effort in most mailers to reply to the included
211 message, and so would usually only be done deliberately, rather
217 is specified, then this copy is filtered
220 prior to being sent to the blind recipients.
221 Alternately, if you specify the
226 use the MIME rules for encapsulation.
228 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
229 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
230 If the environment variable
232 is set, then its value
233 is used as your personal name when constructing the \*(lqFrom:\*(rq
234 line of the message. If this environment variable is not set, then
236 will consult the profile entry \*(lqSignature\*(rq for
240 is specified, then a \*(lqMessage\-ID:\*(rq field will also
241 be added to the message.
245 is re\-distributing a message (when invoked by
247 then \*(lqResent\-\*(rq will be prepended to each of these
248 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
249 If the message already contains a \*(lqFrom:\*(rq field, then a
250 \*(lqSender: user@local\*(rq field will be added as well. (An already
251 existing \*(lqSender:\*(rq field is an error!)
255 switch, each of the entries in the \*(lqTo:\*(rq
256 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
257 format entries. This standard format is designed to be usable by all
258 of the message handlers on the various systems around the Internet.
261 is given, then headers are output exactly as they appear
262 in the message draft.
264 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
265 to the specified folder for the sender in the format in which it will
266 appear to any non\-Bcc receivers of the message. That is, it will have
267 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
268 will be removed from all outgoing copies of the message.
273 switch, the user can direct
275 as to how long it should make header lines containing addresses.
279 has been compiled with SASL support, the
282 the use of SASL authentication with the SMTP MTA. Depending on the
283 SASL mechanism used, this may require an additional password prompt from the
285 .RI \*(lq \&.netrc \*(rq
286 file can be used to store this password).
288 switch can be used to select a particular SASL mechanism,
291 switch can be used to select a authorization userid
292 to provide to SASL other than the default.
294 Currently SASL security layers are not supported for SMTP.
297 will always negotiate an unencrypted connection. This means that while the SMTP
298 authentication can be encrypted, the subsequent data stream can not. This is in
301 POP3 SASL support, where encryption is supported for both the
302 authentication and the data stream.
304 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
305 additional alias files given by the
309 read (more than one file, each preceded by
314 for more information.
319 .ta \w'%etcdir%/ExtraBigFileName 'u
320 ^$HOME/\&.mh\(ruprofile~^The user profile
323 .SH "PROFILE COMPONENTS"
327 .ta \w'ExtraBigProfileName 'u
328 ^Path:~^To determine the user's nmh directory
329 ^Draft\-Folder:~^To find the default draft\-folder
330 ^Aliasfile:~^For a default alias file
331 ^Signature:~^To determine the user's mail signature
332 ^mailproc:~^Program to post failure notices
333 ^postproc:~^Program to post the message
337 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
341 .RB ` file "' defaults to <mh\-dir>/draft"
342 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
343 .RB ` \-nodraftfolder '
352 .RB ` "\-width\ 72" '
359 Under some configurations, it is not possible to monitor the mail delivery
362 is a no-op on those systems.
367 doesn't work correctly.