DIST(1) BSD Reference Manual DIST(1)
dist - redistribute a message to additional addresses
S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
dist [+folder] [msg] [-annotate] [-noannotate]
[-draftfolder +folder] [-draftmessage msg]
[-nodraftfolder] [-editor editor] [-noedit]
[-form formfile] [-inplace] [-noinplace]
[-whatnowproc program] [-nowhatnowproc] [-help]
D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
_
\bD_
\bi_
\bs_
\bt is similar to _
\bf_
\bo_
\br_
\bw. It prepares the specified mes-
sage for redistribution to addresses that (presumably) are
not on the original address list.
The default message form contains the following elements:
If the file named "distcomps" exists in the user's MH
directory, it will be used instead of this form. In
either case, the file specified by `-form formfile' will
be used if given. The form used will be prepended to the
If the draft already exists, _
\bd_
\bi_
\bs_
\bt will ask you as to the
disposition of the draft. A reply of q
\bqu
\bui
\bit
\bt will abort
_
\bd_
\bi_
\bs_
\bt, leaving the draft intact; r
\bre
\bep
\bpl
\bla
\bac
\bce
\be will replace the
existing draft with a blank skeleton; and l
\bli
\bis
\bst
\bt will dis-
Only those addresses in "Resent-To:", "Resent-cc:", and
"Resent-Bcc:" will be sent. Also, a "Resent-Fcc: folder"
will be honored (see _
\bs_
\be_
\bn_
\bd (1)). Note that with _
\bd_
\bi_
\bs_
\bt, the
draft should contain only "Resent-xxx:" fields and no
body. The headers and the body of the original message
are copied to the draft when the message is sent. Use
care in constructing the headers for the redistribution.
If the `-annotate' switch is given, the message being
distributed will be annotated with the lines:
where each address list contains as many lines as
required. This annotation will be done only if the mes-
sage is sent directly from _
\bd_
\bi_
\bs_
\bt. If the message is not
sent immediately from _
\bd_
\bi_
\bs_
\bt, "comp -use" may be used to
re-edit and send the constructed message, but the
DIST(1) BSD Reference Manual DIST(1)
annotations won't take place. The '-inplace' switch
causes annotation to be done in place in order to preserve
links to the annotated message.
See _
\bc_
\bo_
\bm_
\bp (1) for a description of the `-editor' and
`-noedit' switches. Note that while in the editor, the
message being resent is available through a link named "@"
(assuming the default _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw_
\bp_
\br_
\bo_
\bc ). In addition, the
actual pathname of the message is stored in the envariable
$
\b$e
\bed
\bdi
\bit
\bta
\bal
\blt
\bt, and the pathname of the folder containing the
message is stored in the envariable $
\b$m
\bmh
\bhf
\bfo
\bol
\bld
\bde
\ber
\br.
The `-draftfolder +folder' and `-draftmessage msg'
switches invoke the _
\bM_
\bH draft folder facility. This is an
advanced (and highly useful) feature. Consult the
A
\bAd
\bdv
\bva
\ban
\bnc
\bce
\bed
\bd F
\bFe
\bea
\bat
\btu
\bur
\bre
\bes
\bs section of the _
\bM_
\bH manual for more infor-
Upon exiting from the editor, _
\bd_
\bi_
\bs_
\bt will invoke the _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw
program. See _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw (1) for a discussion of available
options. The invocation of this program can be inhibited
by using the `-nowhatnowproc' switch. (In truth of fact,
it is the _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw program which starts the initial edit.
Hence, `-nowhatnowproc' will prevent any edit from occur-
/usr/contrib/mh-6.8/lib/distcomps The message skeleton
or <mh-dir>/distcomps Rather than the standard skeleton
$HOME/.mh_profile The user profile
<mh-dir>/draft The draft file
P
\bPR
\bRO
\bOF
\bFI
\bIL
\bLE
\bE C
\bCO
\bOM
\bMP
\bPO
\bON
\bNE
\bEN
\bNT
\bTS
\bS
Path: To determine the user's MH directory
Current-Folder: To find the default current folder
Draft-Folder: To find the default draft-folder
Editor: To override the default editor
fileproc: Program to refile the message
whatnowproc: Program to ask the "What now?" questions
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
comp(1), forw(1), repl(1), send(1), whatnow(1)
D
\bDE
\bEF
\bFA
\bAU
\bUL
\bLT
\bTS
\bS
`+folder' defaults to the current folder
DIST(1) BSD Reference Manual DIST(1)
C
\bCO
\bON
\bNT
\bTE
\bEX
\bXT
\bT
If a folder is given, it will become the current folder.
The message distributed will become the current message.
H
\bHI
\bIS
\bST
\bTO
\bOR
\bRY
\bY
_
\bD_
\bi_
\bs_
\bt originally used headers of the form "Distribute-xxx:"
instead of "Resent-xxx:". In order to conform with the
ARPA Internet standard, RFC-822, the "Resent-xxx:" form is
now used. _
\bD_
\bi_
\bs_
\bt will recognize "Distribute-xxx:" type
headers and automatically convert them to "Resent-xxx:".
_
\bD_
\bi_
\bs_
\bt does not _
\br_
\bi_
\bg_
\bo_
\br_
\bo_
\bu_
\bs_
\bl_
\by check the message being dis-
tributed for adherence to the transport standard, but _
\bp_
\bo_
\bs_
\bt
called by _
\bs_
\be_
\bn_
\bd does. The _
\bp_
\bo_
\bs_
\bt program will balk (and
rightly so) at poorly formatted messages, and _
\bd_
\bi_
\bs_
\bt won't
If _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw_
\bp_
\br_
\bo_
\bc is _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw, then _
\bd_
\bi_
\bs_
\bt uses a built-in _
\bw_
\bh_
\ba_
\bt_
\b-
_
\bn_
\bo_
\bw, it does not actually run the _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw program. Hence,
if you define your own _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw_
\bp_
\br_
\bo_
\bc, don't call it _
\bw_
\bh_
\ba_
\bt_
\bn_
\bo_
\bw
since _
\bd_
\bi_
\bs_
\bt won't run it.
If your current working directory is not writable, the
link named "@" is not available.
projects / unix-history / blob