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
188 composition file. Note that
192 automatically, unless you
193 add this line to your
203 Otherwise, you must specifically give the command
211 prior to sending the draft.
215 man page for more information.
220 switch indicates the editor to use for the
221 initial edit. Upon exiting from the editor,
228 available options. The invocation of this program can be inhibited
231 switch. (In truth of fact, it is
234 program which starts the initial edit. Hence,
236 will prevent any edit from occurring.)
240 switch is intended to be used by the Emacs mh-e interface to
242 and is only present if
244 was compiled with support for mh-e. It implies
245 .BR \-nowhatnowproc .
246 It causes a file `draft' in the mail storage root
247 to be created, containing the draft message that would normally be presented
248 to the user for editing.
249 No mail is actually sent. Note that this switch is not guaranteed to
250 be present or to have the same effects in future versions of
252 it is documented here only for completeness.
257 switch specifies the message to be forwarded as an
258 exact filename rather than as an
260 folder and message number. It is
261 intended to be used by the
267 The forwarded message is simply
268 copied verbatim into the draft; the processing implied by
274 switches is bypassed, and the usual leading and
275 trailing 'Forwarded Message' delimiters are not added.
276 The same caveats apply to this option as to the
288 switches implement a digest facility for
290 Specifying these switches enables and/or overloads the following escapes:
294 .ta \w'Component 'u +\w'Escape 'u +\w'Returns 'u
295 .I Type Escape Returns Description
296 component digest string Argument to `\-digest'
297 function cur integer Argument to `\-volume'
298 function msg integer Argument to `\-issue'
303 .I "Advanced Features"
306 User's Manual for more information on making digests.
311 .ta \w'%etcdir%/ExtraBigFileName 'u
312 ^%etcdir%/forwcomps~^The standard message skeleton
313 ^or $HOME/.mmh/forwcomps~^Rather than the standard skeleton
314 ^%etcdir%/digestcomps~^The message skeleton if `\-digest' is given
315 ^or $HOME/.mmh/digestcomps~^Rather than the standard skeleton
316 ^%etcdir%/mhl.forward~^The standard message filter
317 ^or $HOME/.mmh/mhl.forward~^Rather than the standard filter
318 ^$HOME/.mmh/profile~^The user profile
319 ^+drafts~^The draft folder
322 .SH "PROFILE COMPONENTS"
326 .ta \w'ExtraBigProfileName 'u
327 ^Path:~^To determine the user's mail storage
328 ^Current\-Folder:~^To find the default current folder
329 ^Draft\-Folder:~^To set the default draft\-folder
330 ^Editor:~^To override the default editor
331 ^Msg\-Protect:~^To set mode when creating a new message (draft)
332 ^fileproc:~^Program to refile the message
333 ^mhlproc:~^Program to filter messages being forwarded
334 ^whatnowproc:~^Program to ask the \*(lqWhat now?\*(rq questions
338 mhbuild(1), comp(1), repl(1), send(1), whatnow(1), mh\-format(5),
339 .I "Proposed Standard for Message Encapsulation"
344 .RB ` +folder "' defaults to the current folder"
345 .RB ` msgs "' defaults to cur"
349 .RB ` \-dashstuffing '
354 If a folder is given, it will become the current folder.
355 The first message forwarded will become the current message.
366 it does not actually run the
369 Hence, if you define your own
379 is told to annotate the messages it forwards, it
380 doesn't actually annotate them until the draft is successfully sent.
387 it's possible to confuse
389 by re\-ordering the file (e.g. by using
392 before the message is successfully sent.
396 don't have this problem.