4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
11 .RB [ \-verbose " | " \-noverbose ]
18 will cause each of the specified messages to be delivered
19 to each of the destinations in the `To:', `Cc:',
20 `Bcc:', `Dcc:', and `Fcc:' fields of the message. If
22 is re\-distributing a message, as invoked from
25 corresponding `Resent\-xxx' fields are examined instead.
30 to do the actual delivery of the messages.
31 Most of the features attributed to
33 are actually performed by
36 The draft is scanned for attachment header fields.
37 Their name defaults to ``Attach'', but may be changed by the value of the
40 If such header fields are found, or the body contains non-ASCII characters,
41 the message is converted to a MIME message.
42 This conversion occurs before all other processing.
44 The first part of the MIME message is the draft body if the body is non-empty.
45 The body of each attachment header field is interpreted as a file name,
46 and each file named is included as a separate part in the MIME message.
48 The MIME type of each file is determined by the MIME type query program,
52 Mmh distributes the program
54 in case no better alternative is available on the system.
56 The last component of the path name is taken as the name of the MIME parts.
57 A message part header for an attachment might be:
60 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
61 Content-Description: VERSION
62 Content-Disposition: attachment; filename="VERSION"
69 will request verbose information of the transport system.
74 argument will send the current message in the draft folder.
76 always takes messages from the draft folder.
79 argument might be added in the future.)
82 man page for more information.
84 Once the transport system has successfully accepted custody of the
85 message, the message will be moved into the trash folder.
86 If there are errors in the formatting of the message,
89 (hopefully) helpful error message.
91 If a `Bcc:' field is encountered, its addresses will be used for
92 delivery, and the `Bcc:' field will be removed from the message
93 sent to sighted recipients. The blind recipients will receive an entirely
94 new message with a minimal set of headers. Included in the body of the
95 message will be a copy of the message sent to the sighted recipients.
97 If a `Dcc:' field is encountered, its addresses will be used for
98 delivery, and the `Dcc:' field will be removed from the message. The
99 blind recipients will receive the same message sent to the sighted
100 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
101 explicit indication that they have received a `blind copy'.
102 This can cause blind recipients to
103 inadvertently reply to all of the sighted recipients of the
104 original message, revealing that they received a blind copy.
105 On the other hand, since a normal reply to a message sent
107 will generate a reply only to the sender of the original message,
108 it takes extra effort in most mailers to reply to the included
109 message, and so would usually only be done deliberately, rather
112 Prior to sending the message, the fields `From:\ user@local',
113 and `Date:\ now' will be appended to the headers in the message.
114 If the environment variable
116 is set, then its value
117 is used as your personal name when constructing the `From:'
118 line of the message. If this environment variable is not set, then
120 will consult the profile entry `Signature' for
125 is re\-distributing a message (when invoked by
127 then `Resent\-' will be prepended to each of these
128 fields: `From:', `Date:', and `Message\-ID:'.
129 If the message already contains a `From:' field, then a
130 `Sender: user@local' field will be added as well. (An already
131 existing `Sender:' field is an error!)
133 If an `Fcc:\ folder' is encountered, the message will be copied
134 to the specified folder for the sender in the format in which it will
135 appear to any non\-Bcc receivers of the message. That is, it will have
136 the appended fields and field reformatting. The `Fcc:' fields
137 will be removed from all outgoing copies of the message.
139 The files specified by the profile entry `Aliasfile:' will be read.
142 for more information.
147 .ta \w'%etcdir%/ExtraBigFileName 'u
148 ^$HOME/.mmh/profile~^The user profile
149 ^+drafts~^The draft folder
152 .SH "PROFILE COMPONENTS"
156 .ta \w'ExtraBigProfileName 'u
157 ^Path:~^To determine the user's mail storage
158 ^Draft\-Folder:~^To set the default draft\-folder
159 ^Aliasfile:~^For a default alias file
160 ^Signature:~^To determine the user's mail signature
161 ^Attachment\-Header:~^To set the name of the attachment header field
162 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
166 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)
170 .RB ` msgs "' defaults to the current message in the draft folder"
projects / mmh / blob