4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
11 .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
37 The draft is scanned for attachment header fields.
38 Their name defaults to ``Attach'', but may be changed by the value of the
41 If such header fields are found, or the body contains non-ASCII characters,
42 the message is converted to a MIME message.
43 This conversion occurs before all other processing.
45 The first part of the MIME message is the draft body if the body is non-empty.
46 The body of each attachment header field is interpreted as a file name,
47 and each file named is included as a separate part in the MIME message.
49 The MIME type of each file is determined by the MIME type query program,
53 Mmh distributes the program
55 in case no better alternative is available on the system.
57 The last component of the path name is taken as the name of the MIME parts.
58 A message part header for an attachment might be:
61 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
62 Content-Description: VERSION
63 Content-Disposition: attachment; filename="VERSION"
70 will request verbose information of the transport system.
75 argument will send the current message in the draft folder.
77 always takes messages from the draft folder.
80 argument might be added in the future.)
83 man page for more information.
85 Once the transport system has successfully accepted custody of the
86 message, the message will be moved into the trash folder.
87 If there are errors in the formatting of the message,
90 (hopefully) helpful error message.
92 If a `Bcc:' field is encountered, its addresses will be used for
93 delivery, and the `Bcc:' field will be removed from the message
94 sent to sighted recipients. The blind recipients will receive an entirely
95 new message with a minimal set of headers. Included in the body of the
96 message will be a copy of the message sent to the sighted recipients.
98 If a `Dcc:' field is encountered, its addresses will be used for
99 delivery, and the `Dcc:' field will be removed from the message. The
100 blind recipients will receive the same message sent to the sighted
101 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
102 explicit indication that they have received a `blind copy'.
103 This can cause blind recipients to
104 inadvertently reply to all of the sighted recipients of the
105 original message, revealing that they received a blind copy.
106 On the other hand, since a normal reply to a message sent
108 will generate a reply only to the sender of the original message,
109 it takes extra effort in most mailers to reply to the included
110 message, and so would usually only be done deliberately, rather
113 Prior to sending the message, the fields `From:\ user@local',
114 and `Date:\ now' will be appended to the headers in the message.
115 If the environment variable
117 is set, then its value
118 is used as your personal name when constructing the `From:'
119 line of the message. If this environment variable is not set, then
121 will consult the profile entry `Signature' for
126 is re\-distributing a message (when invoked by
128 then `Resent\-' will be prepended to each of these
129 fields: `From:', `Date:', and `Message\-ID:'.
130 If the message already contains a `From:' field, then a
131 `Sender: user@local' field will be added as well. (An already
132 existing `Sender:' field is an error!)
134 If an `Fcc:\ folder' is encountered, the message will be copied
135 to the specified folder for the sender in the format in which it will
136 appear to any non\-Bcc receivers of the message. That is, it will have
137 the appended fields and field reformatting. The `Fcc:' fields
138 will be removed from all outgoing copies of the message.
140 The files specified by the profile entry `Aliasfile:' will be read.
143 for more information.
148 .ta \w'%etcdir%/ExtraBigFileName 'u
149 ^$HOME/.mmh/profile~^The user profile
150 ^+drafts~^The draft folder
153 .SH "PROFILE COMPONENTS"
157 .ta \w'ExtraBigProfileName 'u
158 ^Path:~^To determine the user's mail storage
159 ^Draft\-Folder:~^To set the default draft\-folder
160 ^Aliasfile:~^For a default alias file
161 ^Signature:~^To determine the user's mail signature
162 ^Attachment\-Header:~^To set the name of the attachment header field
163 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
167 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)
171 .RB ` msg "' defaults to the current message in the draft folder"