4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
18 .RB [ \-nodraftfolder ]
22 .RB [ \-format " | " \-noformat ]
23 .RB [ \-forward " | " \-noforward ]
24 .RB [ \-mime " | " \-nomime ]
25 .RB [ \-msgid " | " \-nomsgid ]
26 .RB [ \-push " | " \-nopush ]
27 .RB [ \-verbose " | " \-noverbose ]
28 .RB [ \-watch " | " \-nowatch ]
32 .IR port-name/number ]
40 .IR header-field-name ]
42 .IR 0 " | " 1 " | " 2 ]
46 will cause each of the specified files to be delivered
47 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
48 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
50 is re\-distributing a message, as invoked from
53 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
60 delivery of the messages, although this can be changed by defining the
62 profile component. Most of the features attributed to
64 are actually performed by
72 option, the draft is scanned for a header whose field name matches the
74 .IR header-field-name .
75 The draft is converted to a MIME message if one or more matches are found.
76 This conversion occurs before all other processing.
78 The first part of the MIME message is the draft body if that body contains
79 any non-blank characters.
80 The body of each header field whose name matches the
82 is interpreted as a file name, and each file named is included as a separate
83 part in the MIME message.
85 For file names with dot suffixes, the context is scanned for a
87 entry for that suffix.
88 The content-type for the part is taken from that context entry if a match is
90 If no match is found or the file does not have a dot suffix, the content-type
91 is text/plain if the file contains only ASCII characters or application/octet-stream
92 if it contains characters outside of the ASCII range.
94 Each part contains a name attribute that is the last component of the path name.
97 attribute containing the file mode accompanies each part.
98 Finally, a description attribute is generated by running the
104 option specifies the MIME header field formats: a value of
109 attribute as noted above. A value of
111 suppresses both that and the \*(lqContent-Description\*(rq header, and
112 adds a \*(lqContent-Disposition\*(rq header. A value of
116 parameter to the \*(lqContent-Disposition\*(rq header. You can
117 specify one value in your profile, and override it for individual
122 Here are example message part headers, for an attachment, for each of the
128 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
130 Content-Description: ASCII text
133 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
134 Content-Disposition: attachment; filename="VERSION"
137 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
138 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
145 will detach itself from the user's
146 terminal and perform its actions in the background. If
148 and the draft can't be sent, then an error message will be sent (using
149 the mailproc) back to the user. If
151 is given, then a copy
152 of the draft will be attached to this failure notice. Using
156 in the background because the output is
157 trapped and analyzed by
164 will indicate the interactions
165 occurring with the transport system, prior to actual delivery.
170 will monitor the delivery of local
171 and network mail. Hence, by specifying both switches, a large detail
172 of information can be gathered about each step of the message's entry
173 into the transport system.
184 draft folder facility. This is an advanced (and highly
185 useful) feature. Consult the
193 argument will query whether the draft
194 is the intended file, whereas
196 will suppress this question.
197 Once the transport system has successfully accepted custody of the
198 message, the file will be renamed with a leading comma, which allows
199 it to be retrieved until the next draft message is sent. If there are
200 errors in the formatting of the message,
203 (hopefully) helpful error message.
205 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
206 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
207 sent to sighted recipients. The blind recipients will receive an entirely
208 new message with a minimal set of headers. Included in the body of the
209 message will be a copy of the message sent to the sighted recipients.
211 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
212 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
213 blind recipients will receive the same message sent to the sighted
214 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
215 explicit indication that they have received a \*(lqblind copy\*(rq.
216 This can cause blind recipients to
217 inadvertently reply to all of the sighted recipients of the
218 original message, revealing that they received a blind copy.
219 On the other hand, since a normal reply to a message sent
220 via a \*(lqBcc:\*(rq field
221 will generate a reply only to the sender of the original message,
222 it takes extra effort in most mailers to reply to the included
223 message, and so would usually only be done deliberately, rather
229 is specified, then this copy is filtered
232 prior to being sent to the blind recipients.
233 Alternately, if you specify the
238 use the MIME rules for encapsulation.
240 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
241 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
242 If the environment variable
244 is set, then its value
245 is used as your personal name when constructing the \*(lqFrom:\*(rq
246 line of the message. If this environment variable is not set, then
248 will consult the profile entry \*(lqSignature\*(rq for
252 is specified, then a \*(lqMessage\-ID:\*(rq field will also
253 be added to the message.
257 is re\-distributing a message (when invoked by
259 then \*(lqResent\-\*(rq will be prepended to each of these
260 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
261 If the message already contains a \*(lqFrom:\*(rq field, then a
262 \*(lqSender: user@local\*(rq field will be added as well. (An already
263 existing \*(lqSender:\*(rq field is an error!)
267 switch, each of the entries in the \*(lqTo:\*(rq
268 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
269 format entries. This standard format is designed to be usable by all
270 of the message handlers on the various systems around the Internet.
273 is given, then headers are output exactly as they appear
274 in the message draft.
276 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
277 to the specified folder for the sender in the format in which it will
278 appear to any non\-Bcc receivers of the message. That is, it will have
279 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
280 will be removed from all outgoing copies of the message.
285 switch, the user can direct
287 as to how long it should make header lines containing addresses.
289 If nmh is using the SMTP MTA, the
293 switches can be used to override the default mail server (defined by the
299 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
300 additional alias files given by the
304 read (more than one file, each preceded by
309 for more information.
314 .ta \w'%etcdir%/ExtraBigFileName 'u
315 ^$HOME/\&.mh\(ruprofile~^The user profile
318 .SH "PROFILE COMPONENTS"
322 .ta \w'ExtraBigProfileName 'u
323 ^Path:~^To determine the user's nmh directory
324 ^Draft\-Folder:~^To find the default draft\-folder
325 ^Aliasfile:~^For a default alias file
326 ^Signature:~^To determine the user's mail signature
327 ^mailproc:~^Program to post failure notices
328 ^postproc:~^Program to post the message
332 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
336 .RB ` file "' defaults to <mh\-dir>/draft"
337 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
338 .RB ` \-nodraftfolder '
347 .RB ` "\-width\ 72" '
348 .RB ` "\-attachformat\ 0" '
355 Under some configurations, it is not possible to monitor the mail delivery
358 is a no-op on those systems.