4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
13 .RB [ \-verbose " | " \-noverbose ]
19 will cause each of the specified messages to be delivered
20 to each of the destinations in the `To:', `Cc:',
21 `Bcc:', `Dcc:', and `Fcc:' fields of the message. If
23 is re\-distributing a message, as invoked from
26 corresponding `Resent\-xxx' fields are examined instead.
31 to do the actual delivery of the messages.
32 Most of the features attributed to
34 are actually performed by
39 header is already present, the message is converted to a MIME message.
40 In this process, the draft is scanned for attachment header fields.
41 Their name defaults to ``Attach'', but may be changed by the value of the
44 If such header fields are found, the body of each is interpreted as a
45 file name (or a message specification), and each of these files or
46 messages is included as a separate part in the MIME message.
47 (The first part of the MIME message is the draft body.)
50 The MIME type of each file is determined by the MIME type query program,
54 Mmh distributes the program
56 in case no better alternative is available on the system.
58 The last component of the path name is taken as the name of the MIME parts.
59 A message part header for an attachment might be:
62 Content-Type: text/plain; name="README"; charset="us-ascii"
63 Content-Description: README
64 Content-Disposition: attachment; filename="README"
67 This conversion occurs before all other processing.
71 header field is already present in the draft, no such conversion
72 will be done. This way, it is possible to access the full
75 to create elaborate MIME structures, which reach way beyond the
76 attachment system's capabilities.
79 was invoked on the draft beforehand (e.g. at the Whatnow prompt),
82 will use this already MIMEified draft as is.
84 As a second conversion step,
90 header fields, and if found, invokes
92 to sign and encrypt the message. Signing and encrypting is done
93 independently of the MIME conversion.
99 will request verbose information of the transport system.
106 arguments will send the current message in the draft folder.
108 sends messages from the draft folder, unless
113 man page for more information.
115 Once the transport system has successfully accepted custody of the
116 message, the message will be moved into the trash folder.
117 If there are errors in the formatting of the message,
120 (hopefully) helpful error message.
122 If a `Bcc:' field is encountered, its addresses will be used for
123 delivery, and the `Bcc:' field will be removed from the message
124 sent to sighted recipients. The blind recipients will receive an entirely
125 new message with a minimal set of headers. Included in the body of the
126 message will be a copy of the message sent to the sighted recipients.
128 If a `Dcc:' field is encountered, its addresses will be used for
129 delivery, and the `Dcc:' field will be removed from the message. The
130 blind recipients will receive the same message sent to the sighted
131 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
132 explicit indication that they have received a `blind copy'.
133 This can cause blind recipients to
134 inadvertently reply to all of the sighted recipients of the
135 original message, revealing that they received a blind copy.
136 On the other hand, since a normal reply to a message sent
138 will generate a reply only to the sender of the original message,
139 it takes extra effort in most mailers to reply to the included
140 message, and so would usually only be done deliberately, rather
143 Prior to sending the message, the fields `From:\ user@local',
144 and `Date:\ now' will be appended to the headers in the message.
145 If the environment variable
147 is set, then its value
148 is used as your personal name when constructing the `From:'
149 line of the message. If this environment variable is not set, then
151 will consult the profile entry `Signature' for
156 is re\-distributing a message (when invoked by
158 then `Resent\-' will be prepended to each of these
159 fields: `From:', `Date:', and `Message\-ID:'.
160 If the message already contains a `From:' field, then a
161 `Sender: user@local' field will be added as well. (An already
162 existing `Sender:' field is an error!)
164 If an `Fcc:\ folder' is encountered, the message will be copied
165 to the specified folder for the sender in the format in which it will
166 appear to any non\-Bcc receivers of the message. That is, it will have
167 the appended fields and field reformatting. The `Fcc:' fields
168 will be removed from all outgoing copies of the message.
170 The files specified by the profile entry `Aliasfile:' will be read.
173 for more information.
178 .ta \w'%etcdir%/ExtraBigFileName 'u
179 ^$HOME/.mmh/profile~^The user profile
180 ^+drafts~^The draft folder
183 .SH "PROFILE COMPONENTS"
187 .ta \w'ExtraBigProfileName 'u
188 ^Path:~^To determine the user's mail storage
189 ^Draft\-Folder:~^To set the default draft\-folder
190 ^Aliasfile:~^For a default alias file
191 ^Signature:~^To determine the user's mail signature
192 ^Attachment\-Header:~^The name of the attachment header field
193 ^Sign\-Header:~^The name of the sign request header field
194 ^Enc\-Header:~^The name of the encryption request header field
195 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
199 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), mhbuild(1),
204 .RB ` msgs "' defaults to the current message"
205 .RB ` +folder "' defaults to the draft folder"