diplodocus.org Git - nmh/blob - man/post.man

   1 .TH POST %manext8% "August 14, 2016" "%nmhversion%"
   2 .\"
   3 .\" %nmhwarning%
   4 .\"
   5 .SH NAME
   6 post \- deliver a message
   7 .SH SYNOPSIS
   8 .HP 5
   9 .na
  10 .B %nmhlibexecdir%/post
  11 .RB [ \-alias
  12 .IR aliasfile ]
  13 .RB [ \-filter
  14 .IR filterfile ]
  15 .RB [ \-nofilter ]
  16 .RB [ \-format " | " \-noformat ]
  17 .RB [ \-mime " | " \-nomime ]
  18 .RB [ \-msgid " | " \-nomsgid ]
  19 .RB [ \-messageid
  20 .IR localname " | " random ]
  21 .RB [ \-verbose " | " \-noverbose ]
  22 .RB [ \-watch " | " \-nowatch ]
  23 .RB [ \-width
  24 .IR columns ]
  25 .RB [ \-mts
  26 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
  27 .RB [ \-sendmail
  28 .IR program ]
  29 .RB [ \-server
  30 .IR servername ]
  31 .RB [ \-port
  32 .IR portname/number ]
  33 .RB [ \-sasl ]
  34 .RB [ \-nosasl ]
  35 .RB [ \-saslmech
  36 .IR mechanism ]
  37 .RB [ \-user
  38 .IR username ]
  39 .RB [ \-tls ]
  40 .RB [ \-initialtls ]
  41 .RB [ \-notls ]
  42 .I file
  43 .RB [ \-version ]
  44 .RB [ \-help ]
  45 .ad
  46 .SH DESCRIPTION
  47 .B Post
  48 is the default program called by
  49 .B send
  50 to deliver
  51 the message in
  52 .I file
  53 to local and remote users.  In fact, most of
  54 the features attributed to
  55 .B send
  56 in its manual page are performed by
  57 .BR post ,
  58 with
  59 .B send
  60 acting as a relatively simple preprocessor.
  61 Thus, it is
  62 .B post
  63 which parses the various header fields, appends a
  64 \*(lqDate:\*(rq line, and interacts with the mail transport system.
  65 .B Post
  66 will not normally be called directly by the user.
  67 .PP
  68 .B Post
  69 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
  70 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
  71 message for destination addresses, checks these addresses for validity,
  72 and formats them so as to conform to ARPAnet Internet Message Format
  73 protocol, unless the
  74 .B \-noformat
  75 flag is set.  This will normally cause
  76 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
  77 address, as well as any local return addresses.  The
  78 .B \-width
  79 .I columns
  80 switch can be used to indicate the preferred length of the header
  81 components that contain addresses.
  82 .PP
  83 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
  84 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
  85 sent to sighted recipients.  The blind recipients will receive an entirely
  86 new message with a minimal set of headers.  Included in the body of the
  87 message will be a copy of the message sent to the sighted recipients.
  88 If
  89 .B \-filter
  90 .I filterfile
  91 is specified, then this copy is filtered
  92 (re\-formatted) by
  93 .B mhl
  94 prior to being sent to the blind recipients.
  95 Alternately, if the
  96 .B \-mime
  97 switch is given, then
  98 .B post
  99 will use
 100 the MIME rules for encapsulation.
 101 .PP
 102 The
 103 .B \-alias
 104 .I aliasfile
 105 switch can be used to specify a file that post
 106 should take aliases from.  More than one file can be specified, each
 107 being preceded with
 108 .BR \-alias .
 109 In any event, the primary alias file is
 110 read first.
 111 .PP
 112 The
 113 .B \-msgid
 114 switch indicates that a \*(lqMessage\-ID:\*(rq or
 115 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
 116 .PP
 117 The
 118 .B \-messageid
 119 switch selects the style used for the part appearing after the @
 120 in \*(lqMessage\-ID:\*(rq, \*(lqResent\-Message\-ID:\*(rq, and
 121 \*(lqContent\-ID:\*(rq header fields.  The two acceptable options are
 122 .B localname
 123 (which is the default),
 124 and
 125 .BR random .
 126 With
 127 .BR localname ,
 128 the local hostname is used.  With
 129 .BR random ,
 130 a random sequence of characters is used instead.  Note that the
 131 .B \-msgid
 132 switch must be enabled for this switch to have any effect.
 133 .PP
 134 The
 135 .B \-verbose
 136 switch indicates that the user should be informed of
 137 each step of the posting/filing process.
 138 .PP
 139 The
 140 .B \-watch
 141 switch indicates that the user would like to watch the
 142 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
 143 delivery).
 144 .PP
 145 Under normal circumstances,
 146 .B post
 147 uses the \*(lqFrom:\*(rq line in the message draft as the identity of
 148 the originating mailbox.  A \*(lqFrom:\*(rq line is required in
 149 all message draft.  By default the message composition utilities such
 150 as
 151 .BR comp ,
 152 .B repl
 153 and
 154 .B mhmail
 155 will automatically place a \*(lqFrom:\*(rq line in the message draft.
 156 There are two ways to override this behavior, however.
 157 Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
 158 with
 159 .BR dist .
 160 .PP
 161 The first way is to supply a \*(lqSender:\*(rq line.  The value of this
 162 field will be used as the originating mailbox identity when submitting the
 163 message to the mail transport system.  If multiple addresses are
 164 given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq line is
 165 .BR required .
 166 If an \*(lqEnvelope-From:\*(rq line is supplied when multiple addresses
 167 are given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq header will
 168 be generated using the value of the \*(lqEnvelope-From:\*(rq line,
 169 .B if
 170 the \*(lqEnvelope-From:\*(rq line is not blank.
 171 .PP
 172 The second way is to supply a \*(lqEnvelope-From:\*(rq line.  The value
 173 of this field will be used as the originating mailbox identity when
 174 submitting the message to the mail transport system.  This will override
 175 both the value of the \*(lqFrom:\*(rq line and a \*(lqSender:\*(rq line
 176 (if one is supplied).  The \*(lqEnvelope-From:\*(rq line is allowed to
 177 have a blank value; if the value is blank, then the mail transport system
 178 will be instructed to not send any bounces in response to the message.
 179 Not all mail transport systems support this feature.
 180 .PP
 181 The mail transport system default is provided in
 182 .I %nmhetcdir%/mts.conf
 183 but can be overriiden here with the
 184 .B \-mts
 185 switch.
 186 .PP
 187 If nmh is using as its mail transport system
 188 .BR sendmail/pipe ,
 189 the
 190 .B \-sendmail
 191 switch can be used to override the default
 192 .B sendmail
 193 program.
 194 .PP
 195 If nmh is using the SMTP MTA, the
 196 .B \-server
 197 and the
 198 .B \-port
 199 switches can be used to override the default mail server (defined by the
 200 .RI servers
 201 entry in
 202 .I %nmhetcdir%/mts.conf
 203 ).
 204 .PP
 205 If
 206 .B nmh
 207 has been compiled with SASL support, the
 208 .B \-sasl
 209 and
 210 .B \-nosasl
 211 switches will enable and disable
 212 the use of SASL authentication with the SMTP MTA.  Depending on the
 213 SASL mechanism used, this may require an additional password prompt from the
 214 user (but the
 215 .I netrc
 216 file can be used to store this password, as described in the
 217 mh-profile(5) man page).  The
 218 .B \-saslmech
 219 switch can be used to select a particular SASL mechanism,
 220 and the
 221 .B \-user
 222 switch can be used to select a authorization userid to provide to SASL
 223 other than the default.  The credentials profile entry in the
 224 mh\-profile(5) man page describes the ways to supply a username and
 225 password.
 226 .PP
 227 If SASL authentication is successful,
 228 .BR nmh
 229 will attempt to negotiate a security layer for session encryption.
 230 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
 231 viewing the SMTP transaction with the
 232 .B \-snoop
 233 switch.
 234 Base64-encoded data is wrapped with `b64<>'.
 235 (Beware that the SMTP transaction may contain authentication information either
 236 in plaintext or easily decoded base64.)
 237 .PP
 238 If
 239 .B nmh
 240 has been compiled with TLS support, the
 241 .B \-tls
 242 and
 243 .B \-initialtls
 244 switches will require the negotiation of TLS when
 245 connecting to the SMTP MTA.  The
 246 .B \-tls
 247 switch will negotiate TLS as part of the normal SMTP protocol
 248 using the STARTTLS command.  The
 249 .B \-initialtls
 250 will negotiate TLS immediately after the connection has
 251 taken place, before any SMTP commands are sent or received.  Encrypted data
 252 is labelled with `(tls-encrypted)' and
 253 `(tls-decrypted)' when viewing the SMTP transction with the
 254 .B \-snoop
 255 switch.
 256 Base64-encoded data is wrapped with `b64<>'.
 257 (Beware that the SMTP transaction may contain authentication information either
 258 in plaintext or easily decoded base64.)
 259 The
 260 .B \-notls
 261 switch will disable all attempts to negotiate TLS.
 262 .PP
 263 If port 465 is specified and none of the TLS switches were enabled,
 264 .B \-initialtls
 265 will be implied if TLS support was compiled in.  Though port 465 for
 266 SMTPS (SMTP over SSL) was deregistered by IANA in 1998, it is still
 267 used for that service.
 268 .SH FILES
 269 .fc ^ ~
 270 .nf
 271 .ta \w'%nmhetcdir%/ExtraBigFileName  'u
 272 ^%nmhetcdir%/mts.conf~^nmh mts configuration file
 273 ^%nmhetcdir%/MailAliases~^global nmh alias file
 274 ^%bindir%/refile~^Program to process Fcc:s
 275 ^%nmhlibexecdir%/mhl~^Program to process Bcc:s
 276 .fi
 277 .SH "PROFILE COMPONENTS"
 278 .B post
 279 does
 280 .B NOT
 281 consult the user's
 282 .I \&.mh\(ruprofile
 283 .SH "SEE ALSO"
 284 .IR mhmail (1),
 285 .IR send (1),
 286 .IR mh\-mail (5),
 287 .IR mh\-alias (5),
 288 .IR mh\-profile (5),
 289 .IR mh\-tailor (5)
 290 .PP
 291 .I "Standard for the Format of ARPA Internet Text Messages"
 292 (RFC 822)
 293 .SH DEFAULTS
 294 .nf
 295 .RB ` \-alias "' defaults to %nmhetcdir%/MailAliases"
 296 .RB ` \-format '
 297 .RB ` \-nomime '
 298 .RB ` \-nomsgid '
 299 .RB ` "\-messageid\ localname" '
 300 .RB ` \-noverbose '
 301 .RB ` \-nowatch '
 302 .RB ` "\-width\ 72" '
 303 .RB ` \-nofilter '
 304 .fi
 305 .SH CONTEXT
 306 None
 307 .SH BUGS
 308 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
 309 to the RFC 822 specification, but
 310 .B post
 311 won't let you use them.