4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
13 .RB [ \-verbose " | " \-noverbose ]
14 .RB [ \-watch " | " \-nowatch ]
22 will cause each of the specified messages to be delivered
23 to each of the destinations in the `To:', `Cc:',
24 `Bcc:', `Dcc:', and `Fcc:' fields of the message. If
26 is re\-distributing a message, as invoked from
29 corresponding `Resent\-xxx' fields are examined instead.
34 to do the actual delivery of the messages.
35 Most of the features attributed to
37 are actually performed by
40 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, or the body contains non-ASCII characters,
45 the message is converted to a MIME message.
46 This conversion occurs before all other processing.
48 The first part of the MIME message is the draft body if the body is non-empty.
49 The body of each attachment header field is interpreted as a file name,
50 and each file named is included as a separate part in the MIME message.
52 The MIME type of each file is determined by the MIME type query program,
56 Mmh distributes the program
58 in case no better alternative is available on the system.
60 The last component of the path name is taken as the name of the MIME parts.
61 A message part header for an attachment might be:
64 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
65 Content-Description: VERSION
66 Content-Disposition: attachment; filename="VERSION"
73 will indicate the interactions
74 occurring with the transport system, prior to actual delivery.
79 will monitor the delivery of local
80 and network mail. Hence, by specifying both switches, a large detail
81 of information can be gathered about each step of the message's entry
82 into the transport system.
87 argument will send the current message in the draft folder.
89 always takes messages from the draft folder.
92 argument might be added in the future.)
95 man page for more information.
97 Once the transport system has successfully accepted custody of the
98 message, the message will be renamed with a leading comma, which allows
99 it to be retrieved until the next draft message is sent. If there are
100 errors in the formatting of the message,
103 (hopefully) helpful error message.
105 If a `Bcc:' field is encountered, its addresses will be used for
106 delivery, and the `Bcc:' field will be removed from the message
107 sent to sighted recipients. The blind recipients will receive an entirely
108 new message with a minimal set of headers. Included in the body of the
109 message will be a copy of the message sent to the sighted recipients.
111 If a `Dcc:' field is encountered, its addresses will be used for
112 delivery, and the `Dcc:' field will be removed from the message. The
113 blind recipients will receive the same message sent to the sighted
114 recipients. *WARNING* Recipients listed in the `Dcc:' field receive no
115 explicit indication that they have received a `blind copy'.
116 This can cause blind recipients to
117 inadvertently reply to all of the sighted recipients of the
118 original message, revealing that they received a blind copy.
119 On the other hand, since a normal reply to a message sent
121 will generate a reply only to the sender of the original message,
122 it takes extra effort in most mailers to reply to the included
123 message, and so would usually only be done deliberately, rather
126 Prior to sending the message, the fields `From:\ user@local',
127 and `Date:\ now' will be appended to the headers in the message.
128 If the environment variable
130 is set, then its value
131 is used as your personal name when constructing the `From:'
132 line of the message. If this environment variable is not set, then
134 will consult the profile entry `Signature' for
139 is re\-distributing a message (when invoked by
141 then `Resent\-' will be prepended to each of these
142 fields: `From:', `Date:', and `Message\-ID:'.
143 If the message already contains a `From:' field, then a
144 `Sender: user@local' field will be added as well. (An already
145 existing `Sender:' field is an error!)
147 If an `Fcc:\ folder' is encountered, the message will be copied
148 to the specified folder for the sender in the format in which it will
149 appear to any non\-Bcc receivers of the message. That is, it will have
150 the appended fields and field reformatting. The `Fcc:' fields
151 will be removed from all outgoing copies of the message.
153 The files specified by the profile entry `Aliasfile:' and any
154 additional alias files given by the
158 read (more than one file, each preceded by
163 for more information.
168 .ta \w'%etcdir%/ExtraBigFileName 'u
169 ^$HOME/.mmh/profile~^The user profile
170 ^+drafts~^The draft folder
173 .SH "PROFILE COMPONENTS"
177 .ta \w'ExtraBigProfileName 'u
178 ^Path:~^To determine the user's mail storage
179 ^Draft\-Folder:~^To set the default draft\-folder
180 ^Aliasfile:~^For a default alias file
181 ^Signature:~^To determine the user's mail signature
182 ^Attachment\-Header:~^To set the name of the attachment header field
183 ^Mime\-Type\-Query:~^Program to determine the MIME types of files
187 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)
191 .RB ` msg "' defaults to the current message in the draft folder"
200 Under some configurations, it is not possible to monitor the mail delivery
203 is a no-op on those systems.
projects / mmh / blob