4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
13 .RB [ \-verbose " | " \-noverbose ]
21 will cause each of the specified messages to be delivered
22 to each of the destinations in the `To:', `Cc:',
23 `Bcc:', `Dcc:', and `Fcc:' fields of the message. If
25 is re\-distributing a message, as invoked from
28 corresponding `Resent\-xxx' fields are examined instead.
33 to do the actual delivery of the messages.
34 Most of the features attributed to
36 are actually performed by
39 The draft is scanned for attachment header fields.
40 Their name defaults to ``Attach'', but may be changed by the value of the
43 If such header fields are found, or the body contains non-ASCII characters,
44 the message is converted to a MIME message.
45 This conversion occurs before all other processing.
47 The first part of the MIME message is the draft body if the body is non-empty.
48 The body of each attachment header field is interpreted as a file name,
49 and each file named is included as a separate part in the MIME message.
51 The MIME type of each file is determined by the MIME type query program,
55 Mmh distributes the program
57 in case no better alternative is available on the system.
59 The last component of the path name is taken as the name of the MIME parts.
60 A message part header for an attachment might be:
63 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
64 Content-Description: VERSION
65 Content-Disposition: attachment; filename="VERSION"
72 will request verbose information of the transport system.
77 argument will send the current message in the draft folder.
79 always takes messages from the draft folder.
82 argument might be added in the future.)
85 man page for more information.
87 Once the transport system has successfully accepted custody of the
88 message, the message will be renamed with a leading comma, which allows
89 it to be retrieved until the next draft message is sent. If there are
90 errors in the formatting of the message,
93 (hopefully) helpful error message.
95 If a `Bcc:' field is encountered, its addresses will be used for
96 delivery, and the `Bcc:' field will be removed from the message
97 sent to sighted recipients. The blind recipients will receive an entirely
98 new message with a minimal set of headers. Included in the body of the
99 message will be a copy of the message sent to the sighted recipients.
101 If a `Dcc:' field is encountered, its addresses will be used for
102 delivery, and the `Dcc:' field will be removed from the message. The
103 blind recipients will receive the same message sent to the sighted
104 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
105 explicit indication that they have received a `blind copy'.
106 This can cause blind recipients to
107 inadvertently reply to all of the sighted recipients of the
108 original message, revealing that they received a blind copy.
109 On the other hand, since a normal reply to a message sent
111 will generate a reply only to the sender of the original message,
112 it takes extra effort in most mailers to reply to the included
113 message, and so would usually only be done deliberately, rather
116 Prior to sending the message, the fields `From:\ user@local',
117 and `Date:\ now' will be appended to the headers in the message.
118 If the environment variable
120 is set, then its value
121 is used as your personal name when constructing the `From:'
122 line of the message. If this environment variable is not set, then
124 will consult the profile entry `Signature' for
129 is re\-distributing a message (when invoked by
131 then `Resent\-' will be prepended to each of these
132 fields: `From:', `Date:', and `Message\-ID:'.
133 If the message already contains a `From:' field, then a
134 `Sender: user@local' field will be added as well. (An already
135 existing `Sender:' field is an error!)
137 If an `Fcc:\ folder' is encountered, the message will be copied
138 to the specified folder for the sender in the format in which it will
139 appear to any non\-Bcc receivers of the message. That is, it will have
140 the appended fields and field reformatting. The `Fcc:' fields
141 will be removed from all outgoing copies of the message.
143 The files specified by the profile entry `Aliasfile:' and any
144 additional alias files given by the
148 read (more than one file, each preceded by
153 for more information.
158 .ta \w'%etcdir%/ExtraBigFileName 'u
159 ^$HOME/.mmh/profile~^The user profile
160 ^+drafts~^The draft folder
163 .SH "PROFILE COMPONENTS"
167 .ta \w'ExtraBigProfileName 'u
168 ^Path:~^To determine the user's mail storage
169 ^Draft\-Folder:~^To set the default draft\-folder
170 ^Aliasfile:~^For a default alias file
171 ^Signature:~^To determine the user's mail signature
172 ^Attachment\-Header:~^To set the name of the attachment header field
173 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
177 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)
181 .RB ` msg "' defaults to the current message in the draft folder"