4 .TH FORW %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 forw \- forward messages
13 .RB [ \-annotate " | " \-noannotate ]
16 .RB [ \-format " | " \-noformat ]
19 .RB [ \-inplace " | " \-noinplace ]
20 .RB [ \-mime " | " \-nomime ]
26 .RB [ \-nowhatnowproc ]
27 .RB [ \-dashstuffing " | " \-nodashstuffing ]
44 [other\ switches\ for\
51 may be used to prepare a message containing other messages.
53 It constructs the new message from a forms (components) file, with a
54 body composed of the message(s) to be forwarded. An editor is invoked
57 and after editing is complete, the user is prompted
58 before the message is sent.
60 The default message form contains the following elements:
69 .RI \*(lq forwcomps \*(rq
70 exists in the user's mmh directory,
71 it will be used instead of this default form. You may also specify an
72 alternate forms file with the switch
78 switch is given, each message being forwarded will
79 be annotated with the lines:
88 where each address list contains as many lines as required. This
89 annotation will be done only if the message is sent directly from
91 If the message is not sent immediately from
95 may be used to re\-edit and send the constructed
96 message, but the annotations won't take place. Normally annotations
97 are done inplace in order to preserve any links to the message. You may
98 change this by using the
104 for a description of the
112 uses a forms (components) file to direct it how to
113 construct the beginning of the draft, it uses a message filter file to
114 direct it as to how each forwarded message should be formatted in the
115 body of the draft. The filter file for \fIforw\fR should be a standard
122 to filter (re\-format) the forwarded messages prior to being output to
123 the body of the draft.
131 specify which message filter file to use.
135 is specified (this is the default), then each forwarded
136 message is output into the draft exactly as it appears with no
142 is specified, then a default message filter file is used.
143 This default message filter should be adequate for most users.
145 .RI \*(lq mhl.forward \*(rq
155 .RI \*(lq mhl.forward \*(rq
156 exists in the user's mmh
157 directory, it will be used instead of this form. You may specify an
158 alternate message filter file with the switch
162 Each forwarded message is separated with an encapsulation delimiter.
163 By default, any dashes in the first column of the forwarded messages
164 will be prepended with `\-\ ' so that when received, the message is
165 suitable for bursting by
167 This follows the Internet RFC\-934 guidelines. You may use the flag
170 to suppress this form of quoting to the forwarded messages.
179 file, any commentary text is entered
180 before the forwarded messages. (A major win!)
182 To use the MIME rules for encapsulation, specify the
186 to generate an attachment header field.
188 will care for everything else.
193 switch indicates the editor to use for the
194 initial edit. Upon exiting from the editor,
201 available options. The invocation of this program can be inhibited
204 switch. (In truth of fact, it is
207 program which starts the initial edit. Hence,
209 will prevent any edit from occurring.)
213 switch is intended to be used by the Emacs mh-e interface to
215 and is only present if
217 was compiled with support for mh-e. It implies
218 .BR \-nowhatnowproc .
219 It causes a file `draft' in the mail storage root
220 to be created, containing the draft message that would normally be presented
221 to the user for editing.
222 No mail is actually sent. Note that this switch is not guaranteed to
223 be present or to have the same effects in future versions of
225 it is documented here only for completeness.
230 switch specifies the message to be forwarded as an
231 exact filename rather than as an
233 folder and message number. It is
234 intended to be used by the
240 The forwarded message is simply
241 copied verbatim into the draft; the processing implied by
247 switches is bypassed, and the usual leading and
248 trailing 'Forwarded Message' delimiters are not added.
249 The same caveats apply to this option as to the
261 switches implement a digest facility for
263 Specifying these switches enables and/or overloads the following escapes:
267 .ta \w'Component 'u +\w'Escape 'u +\w'Returns 'u
268 .I Type Escape Returns Description
269 component digest string Argument to `\-digest'
270 function cur integer Argument to `\-volume'
271 function msg integer Argument to `\-issue'
276 .I "Advanced Features"
279 User's Manual for more information on making digests.
284 .ta \w'%etcdir%/ExtraBigFileName 'u
285 ^%etcdir%/forwcomps~^The standard message skeleton
286 ^or $HOME/.mmh/forwcomps~^Rather than the standard skeleton
287 ^%etcdir%/digestcomps~^The message skeleton if `\-digest' is given
288 ^or $HOME/.mmh/digestcomps~^Rather than the standard skeleton
289 ^%etcdir%/mhl.forward~^The standard message filter
290 ^or $HOME/.mmh/mhl.forward~^Rather than the standard filter
291 ^$HOME/.mmh/profile~^The user profile
292 ^+drafts~^The draft folder
295 .SH "PROFILE COMPONENTS"
299 .ta \w'ExtraBigProfileName 'u
300 ^Path:~^To determine the user's mail storage
301 ^Current\-Folder:~^To find the default current folder
302 ^Draft\-Folder:~^To set the default draft\-folder
303 ^Editor:~^To override the default editor
304 ^Msg\-Protect:~^To set mode when creating a new message (draft)
305 ^fileproc:~^Program to refile the message
306 ^mhlproc:~^Program to filter messages being forwarded
307 ^whatnowproc:~^Program to ask the \*(lqWhat now?\*(rq questions
311 mhbuild(1), comp(1), repl(1), send(1), whatnow(1), mh\-format(5),
312 .I "Proposed Standard for Message Encapsulation"
317 .RB ` +folder "' defaults to the current folder"
318 .RB ` msgs "' defaults to cur"
322 .RB ` \-dashstuffing '
327 If a folder is given, it will become the current folder.
328 The first message forwarded will become the current message.
339 it does not actually run the
342 Hence, if you define your own
352 is told to annotate the messages it forwards, it
353 doesn't actually annotate them until the draft is successfully sent.
360 it's possible to confuse
362 by re\-ordering the file (e.g. by using
365 before the message is successfully sent.
369 don't have this problem.