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 renamed with a leading comma, which allows
87 it to be retrieved until the next draft message is sent. If there are
88 errors in the formatting of the message,
91 (hopefully) helpful error message.
93 If a `Bcc:' field is encountered, its addresses will be used for
94 delivery, and the `Bcc:' field will be removed from the message
95 sent to sighted recipients. The blind recipients will receive an entirely
96 new message with a minimal set of headers. Included in the body of the
97 message will be a copy of the message sent to the sighted recipients.
99 If a `Dcc:' field is encountered, its addresses will be used for
100 delivery, and the `Dcc:' field will be removed from the message. The
101 blind recipients will receive the same message sent to the sighted
102 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
103 explicit indication that they have received a `blind copy'.
104 This can cause blind recipients to
105 inadvertently reply to all of the sighted recipients of the
106 original message, revealing that they received a blind copy.
107 On the other hand, since a normal reply to a message sent
109 will generate a reply only to the sender of the original message,
110 it takes extra effort in most mailers to reply to the included
111 message, and so would usually only be done deliberately, rather
114 Prior to sending the message, the fields `From:\ user@local',
115 and `Date:\ now' will be appended to the headers in the message.
116 If the environment variable
118 is set, then its value
119 is used as your personal name when constructing the `From:'
120 line of the message. If this environment variable is not set, then
122 will consult the profile entry `Signature' for
127 is re\-distributing a message (when invoked by
129 then `Resent\-' will be prepended to each of these
130 fields: `From:', `Date:', and `Message\-ID:'.
131 If the message already contains a `From:' field, then a
132 `Sender: user@local' field will be added as well. (An already
133 existing `Sender:' field is an error!)
135 If an `Fcc:\ folder' is encountered, the message will be copied
136 to the specified folder for the sender in the format in which it will
137 appear to any non\-Bcc receivers of the message. That is, it will have
138 the appended fields and field reformatting. The `Fcc:' fields
139 will be removed from all outgoing copies of the message.
141 The files specified by the profile entry `Aliasfile:' will be read.
144 for more information.
149 .ta \w'%etcdir%/ExtraBigFileName 'u
150 ^$HOME/.mmh/profile~^The user profile
151 ^+drafts~^The draft folder
154 .SH "PROFILE COMPONENTS"
158 .ta \w'ExtraBigProfileName 'u
159 ^Path:~^To determine the user's mail storage
160 ^Draft\-Folder:~^To set the default draft\-folder
161 ^Aliasfile:~^For a default alias file
162 ^Signature:~^To determine the user's mail signature
163 ^Attachment\-Header:~^To set the name of the attachment header field
164 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
168 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)
172 .RB ` msg "' defaults to the current message in the draft folder"