1 .TH DIST %manext1% 2012-12-04 "%nmhversion%"
6 dist \- distribute an nmh message to additional addresses
17 .RB [ \-annotate " | " \-noannotate ]
18 .RB [ \-inplace " | " \-noinplace ]
23 .RB [ \-nodraftfolder ]
39 .RB [ \-nowhatnowproc ]
47 It prepares the specified message
48 for redistribution to addresses that (presumably) are not on the original
51 The default message form contains the following elements:
55 Resent-From: {from switch} or <Local-Mailbox> or <username@hostname>
56 Resent-To: {to switch} or blank
57 Resent-cc: {cc switch} or blank
58 Resent-fcc: {fcc switch} or blank
63 .RI \*(lq distcomps \*(rq
64 exists in the user's nmh directory, it
65 will be used instead of this default form. You may specify an alternate
66 forms file with the switch
69 Forms are processed via the
73 for details. Components from the redistributed message are available
74 as standard component escapes in the forms file.
76 In addition to the standard
78 escapes, the following
80 escapes are also supported:
84 .ta \w'Escape 'u +\w'Returns 'u
85 .I "Escape Returns Description"
86 fcc string Any folders specified with `\-fcc\ folder'
87 nmh\-from string Addresses specified with `\-from\ address'
88 nmh\-to string Addresses specified with `\-to\ address'
89 nmh\-cc string Addresses specified with `\-cc\ address'
95 for descriptions of the
103 If the draft already exists,
105 will ask you as to the disposition of the draft. A reply of
109 leaving the draft intact;
111 will replace the existing draft with a blank skeleton; and
113 will display the draft.
115 Only those addresses in
116 .RI \*(lq Resent\-To: \*(rq,
117 .RI \*(lq Resent\-cc: \*(rq,
119 .RI \*(lq Resent\-Bcc: \*(rq
120 will be sent. Also, a
121 .RI \*(lq "Resent\-Fcc: folder" \*(rq
126 the draft should contain only
127 .RI \*(lq Resent\-xxx: \*(rq
128 fields and no body. The headers and the body of
129 the original message are copied to the draft when the message is sent.
130 Use care in constructing the headers for the redistribution.
132 Because the draft is minimal, the
134 editor is quite useful with
139 switch is given, the message being distributed will
140 be annotated with the lines:
146 where each address list contains as many lines as required. This
147 annotation will be done only if the message is sent directly from
149 If the message is not sent immediately from
153 may be used to re-edit and send the constructed
154 message, but the annotations won't take place. Normally annotations are
155 done in place in order to preserve any links to the message. You may use
158 switch to change this.
162 for a description of the
166 switches. Note that while in the editor, with
168 and if the current directory is writable, the message being resent
169 is available through a link named \*(lq@\*(rq (assuming the default
171 In addition, the actual pathname of the message is
172 stored in the environment variable
175 the folder containing the message is stored in the environment variable
177 The creation of the \*(lq@\*(rq file is controlled via the
191 draft folder facility. This is an advanced (and highly
192 useful) feature. Consult
194 for more information.
196 Upon exiting from the editor,
202 for a discussion of available options. The invocation of this
203 program can be inhibited by using the
205 switch. (In fact, it is the
207 program which starts the initial edit. Hence,
209 will prevent any edit from occurring.)
213 %nmhetcdir%/distcomps
214 The default message skeleton.
217 The user's message skeleton.
225 .SH "PROFILE COMPONENTS"
229 To determine the user's nmh directory.
232 To find the default current folder.
235 To find the default draft-folder.
238 To override the default editor.
241 Program to refile the message.
244 Program to ask the \*(lqWhat now?\*(rq questions.
271 If a folder is given, it will become the current folder. The message
272 distributed will become the current message.
275 originally used headers of the form
276 .RI \*(lq Distribute\-xxx: \*(rq
278 .RI \*(lq Resent\-xxx: \*(rq.
279 In order to conform with the ARPA Internet standard, RFC 822, the
280 .RI \*(lq Resent\-xxx: \*(rq
284 .RI \*(lq Distribute\-xxx: \*(rq
285 type headers and automatically convert them to
286 .RI \*(lq Resent\-xxx: \*(rq.
289 does not rigorously check the message being distributed
290 for adherence to the transport standard, but
296 program will balk (and rightly so) at poorly formatted messages, and
298 won't correct things for you.
308 it does not actually run the
311 Hence, if you define your own