Annotation of 43BSD/contrib/mh/conf/doc/send.rf, revision 1.1.1.1

1.1       root        1: .\"    @(MHWARNING)
                      2: .TH SEND 1 "April 22, 1986" MH [mh.6]
                      3: .UC 6
                      4: .SH NAME
                      5: send \- send a message
                      6: .SH SYNOPSIS
                      7: .in +.5i
                      8: .ti -.5i
                      9: send
                     10: \%[\-alias\ aliasfile]
                     11: \%[\-draft]
                     12: \%[\-draftfolder\ +folder] \%[\-draftmessage\ msg] \%[\-nodraftfolder]
                     13: @BEGIN: TMA
                     14: \%[\-encrypt] \%[\-noencrypt] 
                     15: @END: TMA
                     16: \%[\-filter\ filterfile] \%[\-nofilter]
                     17: \%[\-format] \%[\-noformat]
                     18: \%[\-forward] \%[\-noforward]
                     19: \%[\-msgid] \%[\-nomsgid]
                     20: \%[\-push] \%[\-nopush]
                     21: \%[\-verbose] \%[\-noverbose]
                     22: \%[\-watch] \%[\-nowatch]
                     23: \%[\-width\ columns]
                     24: \%[file\ ...] 
                     25: \%[\-help]
                     26: .in -.5i
                     27: .SH DESCRIPTION
                     28: \fISend\fR will cause each of the specified files to
                     29: be delivered (via \fIpost\fR\0(8)) to each of the destinations
                     30: in the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq, and \*(lqFcc:\*(rq
                     31: fields of the message.
                     32: If \fIsend\fR is re\-distributing a message, as invoked from \fIdist\fR,
                     33: then the corresponding \*(lqResent\-xxx\*(rq fields are examined
                     34: instead.
                     35: 
                     36: If `\-push' is specified,
                     37: \fIsend\fR will detach itself from the user's terminal and perform its
                     38: actions in the background.
                     39: If \fIpush\fR\0'd and the draft can't be sent,
                     40: then the `\-forward' switch says that draft should be forwarded with
                     41: the failure notice sent to the user.
                     42: This differs from putting \fIsend\fR in the background because the output is
                     43: trapped and analyzed by \fIMH\fR.
                     44: 
                     45: If `\-verbose' is specified, \fIsend\fR will indicate the interactions
                     46: occurring with the transport system, prior to actual delivery.
                     47: If `\-watch' is specified \fIsend\fR will monitor the delivery of local and
                     48: network mail.  Hence, by specifying both switches, a large detail of 
                     49: information can be gathered about each step of the message's entry into the
                     50: transport system.
                     51: 
                     52: The `\-draftfolder\ +folder' and `\-draftmessage\ msg' switches invoke the
                     53: \fIMH\fR draft folder facility.
                     54: This is an advanced (and highly useful) feature.
                     55: Consult the \fBAdvanced Features\fR section of the \fIMH\fR manual for more
                     56: information.
                     57: 
                     58: \fISend\fR with no \fIfile\fR
                     59: argument will query whether the draft is the intended file, whereas
                     60: `\-draft' will suppress this question.
                     61: Once the transport system has successfully accepted custody of the message,
                     62: the file will be renamed
                     63: with a leading comma, which allows it to be retrieved until the
                     64: next draft message is sent.
                     65: If there are errors in the
                     66: formatting of the message, \fIsend\fR will abort with a (hopefully)
                     67: helpful error message.
                     68: 
                     69: If a \*(lqBcc:\*(rq field is encountered,
                     70: its addresses will be used for delivery,
                     71: and the \*(lqBcc:\*(rq field will be removed from the message sent to sighted
                     72: recipients.
                     73: The blind recipients will receive an entirely new message with
                     74: a minimal set of headers.
                     75: Included in the body of the message will be a copy of the message sent to the
                     76: sighted recipients.
                     77: If `\-filter\ filterfile' is specified,
                     78: then this copy is filtered (re\-formatted)
                     79: prior to being sent to the blind recipients.
                     80: 
                     81: Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq, and
                     82: \*(lqDate:\ now\*(rq will be appended to the headers in the message.
                     83: If the envariable \fB$SIGNATURE\fR is set,
                     84: then its value is used as your personal name when
                     85: constructing the \*(lqFrom:\*(rq line of the message.
                     86: If this envariable is not set,
                     87: then \fIsend\fR will consult the profile entry \*(lqSignature\*(rq
                     88: for this information.
                     89: On hosts where \fIMH\fR was configured with the UCI option,
                     90: if \fB$SIGNATURE\fR is not set and the \*(lqSignature\*(rq profile entry
                     91: is not present,
                     92: then the file \fB$HOME\fR/.signature is consulted.
                     93: If `\-msgid' is
                     94: specified, then a \*(lqMessage\-ID:\*(rq field will also be added to the
                     95: message.
                     96: 
                     97: If \fIsend\fR is re\-distributing a message
                     98: (when invoked by \fIdist\fR\0),
                     99: then \*(lqResent\-\*(rq will be prepended to each of these fields:
                    100: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
                    101: If the message already contains a \*(lqFrom:\*(rq field, then a
                    102: \*(lqSender: user@local\*(rq field will be added as well.
                    103: (An already existing
                    104: \*(lqSender:\*(rq field is an error!)
                    105: 
                    106: By using the `\-format' switch,
                    107: each of the entries in
                    108: the \*(lqTo:\*(rq and \*(lqcc:\*(rq fields will be replaced
                    109: with \*(lqstandard\*(rq format entries.
                    110: This standard format is designed to be usable by all
                    111: of the message handlers on the various systems around the
                    112: Internet.
                    113: If `\-noformat' is given,
                    114: then headers are output exactly as they appear in the message draft.
                    115: 
                    116: If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
                    117: to the specified folder for the sender in the format in which it will appear
                    118: to any non\-Bcc receivers of the message.
                    119: That is, it will have the appended
                    120: fields and field reformatting.
                    121: The \*(lqFcc:\*(rq fields will be removed from all outgoing copies of the
                    122: message.
                    123: 
                    124: By using the `\-width\ columns' switch, the user can direct \fIsend\fR as to
                    125: how long it should make header lines containing addresses.
                    126: 
                    127: By using the `\-alias\ aliasfile' switch, the user can direct \fIsend\fR
                    128: to consult the named files for alias definitions
                    129: (more than one file, each  preceded by `\-alias', can be named).
                    130: See \fImh\-alias\fR\0(5) for more information.
                    131: .Fi
                    132: ^$HOME/\&.mh\(ruprofile~^The user profile
                    133: .Pr
                    134: ^Path:~^To determine the user's MH directory
                    135: .Ps
                    136: ^Draft\-Folder:~^To find the default draft\-folder
                    137: .Ps
                    138: ^Signature:~^To determine the user's mail signature
                    139: .Ps
                    140: mailproc:~^Program to post failure notices
                    141: .Ps
                    142: ^postproc:~^Program to post the message
                    143: .Sa
                    144: comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
                    145: .De
                    146: `file' defaults to <mh\-dir>/draft
                    147: .Ds
                    148: `\-alias @(MHETCPATH)/MailAliases'
                    149: .Ds
                    150: `\-nodraftfolder'
                    151: @BEGIN: TMA
                    152: `\-noencrypt'
                    153: @END: TMA
                    154: .Ds
                    155: `\-nofilter'
                    156: .Ds
                    157: `\-format'
                    158: .Ds
                    159: `\-forward'
                    160: .Ds
                    161: `\-nomsgid'
                    162: .Ds
                    163: `\-nopush'
                    164: .Ds
                    165: `\-noverbose'
                    166: .Ds
                    167: `\-nowatch'
                    168: .Ds
                    169: `\-width\ 72'
                    170: .Co
                    171: None
                    172: .En

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.