phpMan > info > post(8)

POST(8mh)                                                            POST(8mh)

NAME
       post - deliver an nmh message

SYNOPSIS
       /usr/lib/mh/post [-help] [-version] [-alias aliasfile] [-filter filter-
            file] [-nofilter] [-format | -noformat] [-mime | -nomime] [-msgid
            | -nomsgid] [-messageid localname | random] [-verbose | -nover-
            bose] [-watch | -nowatch] [-width columns] [-mts smtp | send-
            mail/smtp | sendmail/pipe] [-sendmail program] [-server server-
            name] [-port portname/number] [-sasl] [-nosasl] [-saslmech mecha-
            nism] [-user username] [-tls] [-initialtls] [-notls] file

DESCRIPTION
       post  is  the  default program called by send to deliver the message in
       file to local and remote users.  In fact, most of the features  attrib-
       uted to send in its manual page are performed by post, with send acting
       as a relatively simple preprocessor.  Thus, it is post which parses the
       various  header  fields, appends a "Date:" line, and interacts with the
       mail transport system.  post will not normally be  called  directly  by
       the  user, but can be replaced by the user with a postproc profile com-
       ponent that will have file as its final  argument.   See  mh-profile(5)
       for more information on postproc.

       post  searches  the  "To:",  "cc:",  "Bcc:",  "Fcc:", and "Resent-xxx:"
       header lines of the specified message for destination addresses, checks
       these  addresses  for  validity,  and  formats them so as to conform to
       ARPAnet Internet Message Format protocol, unless the -noformat flag  is
       set.  This will normally cause "@local-site" to be appended to each lo-
       cal destination address, as well as any local  return  addresses.   The
       -width  columns  switch can be used to indicate the preferred length of
       the header components that contain addresses.

       If a "Bcc:" field is encountered, its addresses will be used for deliv-
       ery,  and  the  "Bcc:"  field  will be removed from the message sent to
       sighted recipients. The blind recipients will receive an  entirely  new
       message  with  a  minimal  set of headers. The body of this new message
       will contain a copy of the message sent to the sighted recipients,  ei-
       ther  marked up with the indicator text "Blind-Carbon-Copy" or encapsu-
       lated as a MIME digest.

       If -filter filterfile is specified, then this copy is filtered (re-for-
       matted)  by  mhl  prior  to being sent to the blind recipients.  Alter-
       nately, if the -mime switch is given, then post will use the MIME rules
       for encapsulation.

       If  a  "Dcc:" field is encountered and the sendmail/pipe mail transport
       method is not in use, its addresses will be used for delivery, and  the
       "Dcc:"  field  will  be  removed from the message. The blind recipients
       will receive exactly the same message as the sighted recipients. *WARN-
       ING*  Recipients listed in the "Dcc:" field receive no explicit indica-
       tion that they have received a "blind copy".  This can cause blind  re-
       cipients to inadvertently reply to all of the sighted recipients of the
       original message, revealing that they received a blind  copy.   On  the
       other  hand,  since a normal reply to a message sent via a "Bcc:" field
       will generate a reply only to the sender of the  original  message,  it
       takes  extra  effort  in most mailers to reply to the included message,
       and so would usually only be done deliberately, rather  than  by  acci-
       dent.

       post  rejects  all  messages  that  contain a "Dcc:" field if the send-
       mail/pipe mail transport method is used.

       The -alias aliasfile switch can be used to specify  a  file  that  post
       should  read  aliases  from.  More than one file can be specified, with
       each being preceded by -alias.  In any event, the primary alias file is
       read first.

       The  -msgid  switch  indicates  that  a  "Message-ID:"  or "Resent-Mes-
       sage-ID:" field should be added to the header.

       The -messageid switch selects the style used for the part appearing af-
       ter  the  @  in  "Message-ID:", "Resent-Message-ID:", and "Content-ID:"
       header fields.  The two acceptable options are localname (which is  the
       default),  and  random.   With  localname,  the local hostname is used.
       With random, a random sequence of characters  is  used  instead.   Note
       that  the -msgid switch must be enabled for this switch to have any ef-
       fect.

       The -verbose switch indicates that the user should be informed of  each
       step of the posting/filing process.

       The  -watch  switch  indicates  that  the  user would like to watch the
       transport system's handling of the message (e.g., local and "fast"  de-
       livery).

       Under  normal  circumstances, post uses the "From:" line in the message
       draft as the identity of the originating mailbox.  A  "From:"  line  is
       required  in  all  message  drafts.  By default the message composition
       utilities such as comp, repl and  mhmail  will  automatically  place  a
       "From:" line in the message draft.  There are two ways to override this
       behavior, however.  Note that  they  apply  equally  to  "Resent-From:"
       lines in messages sent with dist.

       The  first  way is to supply a "Sender:" line.  The value of this field
       will be used as the originating mailbox identity  when  submitting  the
       message  to the mail transport system.  If multiple addresses are given
       in the "From:" line, a "Sender:" line is required.   If  an  "Envelope-
       From:"  line  is  supplied  when  multiple  addresses  are given in the
       "From:" line, a "Sender:" header will be generated using the  value  of
       the "Envelope-From:" line, if the "Envelope-From:" line is not blank.

       The second way is to supply a "Envelope-From:" line.  The value of this
       field will be used as the originating mailbox identity when  submitting
       the  message to the mail transport system.  This will override both the
       value of the "From:" line and a "Sender:" line (if  one  is  supplied).
       The  "Envelope-From:"  line  is  allowed  to have a blank value; if the
       value is blank, then the mail transport system will  be  instructed  to
       not  send  any bounces in response to the message.  Not all mail trans-
       port systems support this feature.

       The mail transport system default is defined in  /etc/nmh/mts.conf  but
       can be overridden here with the -mts switch.

       If nmh is using sendmail/pipe, as its mail transport system, the -send-
       mail switch can be used to override the default sendmail program.

       If nmh is using the SMTP MTA, the -server and  -port  switches  can  be
       used  to override the default mail server and port.  The default server
       is set with servers in /etc/nmh/mts.conf, and the default port is  sub-
       mission, 587.

       If  nmh  has  been  compiled  with  SASL support, the -sasl and -nosasl
       switches will enable and disable the use of  SASL  authentication  with
       the  SMTP  MTA.  Depending on the SASL mechanism used, this may require
       an additional password prompt from the user (but the netrc file can  be
       used  to  store  this  password,  as  described  in mh-profile(5).  The
       -saslmech switch can be used to select a particular SASL mechanism, and
       the  -user switch can be used to select an authorization userid to pro-
       vide to SASL, other than the default.  The credentials profile entry in
       mh-profile(5) describes the ways to supply a username and password.

       If  SASL  authentication is successful, nmh will attempt to negotiate a
       security layer for session encryption.  Encrypted data is labelled with
       `(sasl-encrypted)'  and `(sasl-decrypted)' when viewing the SMTP trans-
       action with the -snoop switch.  Base64-encoded  data  is  wrapped  with
       `b64<>'.   (Beware that the SMTP transaction may contain authentication
       information either in plaintext or easily decoded base64.)

       If nmh has been compiled with TLS support,  the  -tls  and  -initialtls
       switches  will  require  the  negotiation of TLS when connecting to the
       SMTP MTA.  The -tls switch will negotiate TLS as  part  of  the  normal
       SMTP protocol using the STARTTLS command.  The -initialtls will negoti-
       ate TLS immediately after the connection has taken  place,  before  any
       SMTP  commands  are  sent or received.  Encrypted data is labelled with
       `(tls-encrypted)' and `(tls-decrypted)' when viewing the SMTP  transac-
       tion  with  the  -snoop  switch.   Base64-encoded  data is wrapped with
       `b64<>'.  (Beware that the SMTP transaction may contain  authentication
       information  either in plaintext or easily decoded base64.)  The -notls
       switch will disable all attempts to negotiate TLS.

       If port 465 is specified and none of the  TLS  switches  were  enabled,
       -initialtls  will  be  implied  if TLS support was compiled in.  Though
       port 465 for SMTPS (SMTP over SSL) was deregistered by IANA in 1998, it
       is still used for that service.

       post  filters  out  header lines with names beginning with "Nmh-" (case
       insensitive) from the message draft.  Those lines are reserved for  in-
       ternal nmh use.

FILES
       /etc/nmh/mts.conf          nmh mts configuration file
       /etc/nmh/MailAliases       global nmh alias file
       /usr/bin/mh/refile         Program to process Fcc:s
       /usr/lib/mh/mhl            Program to process Bcc:s

PROFILE COMPONENTS
       post does not consult the user's .mh_profile

SEE ALSO
       mhmail(1),  send(1),  mh-mail(5),  mh-alias(5),  mh-profile(5), mh-tai-
       lor(5)

       Standard for the Format of ARPA Internet Text Messages (RFC 822)

DEFAULTS
       `-alias' defaults to /etc/nmh/MailAliases
       `-format'
       `-nomime'
       `-nomsgid'
       `-messageid localname'
       `-noverbose'
       `-nowatch'
       `-width 72'
       `-nofilter'

CONTEXT
       None

BUGS
       "Reply-To:" fields are allowed to have groups in them according to  the
       RFC 822 specification, but post won't let you use them.

nmh-1.7.1                         2016-10-17                         POST(8mh)
LWP-REQUEST(1p)       User Contributed Perl Documentation      LWP-REQUEST(1p)

NAME
       lwp-request - Simple command line user agent

SYNOPSIS
       lwp-request [-afPuUsSedvhx] [-m method] [-b base URL] [-t timeout]
                   [-i if-modified-since] [-c content-type]
                   [-C credentials] [-p proxy-url] [-o format] url...

DESCRIPTION
       This program can be used to send requests to WWW servers and your local
       file system. The request content for POST and PUT methods is read from
       stdin.  The content of the response is printed on stdout.  Error
       messages are printed on stderr.  The program returns a status value
       indicating the number of URLs that failed.

       The options are:

       -m <method>
           Set which method to use for the request.  If this option is not
           used, then the method is derived from the name of the program.

       -f  Force request through, even if the program believes that the method
           is illegal.  The server might reject the request eventually.

       -b <uri>
           This URI will be used as the base URI for resolving all relative
           URIs given as argument.

       -t <timeout>
           Set the timeout value for the requests.  The timeout is the amount
           of time that the program will wait for a response from the remote
           server before it fails.  The default unit for the timeout value is
           seconds.  You might append "m" or "h" to the timeout value to make
           it minutes or hours, respectively.  The default timeout is '3m',
           i.e. 3 minutes.

       -i <time>
           Set the If-Modified-Since header in the request. If time is the
           name of a file, use the modification timestamp for this file. If
           time is not a file, it is parsed as a literal date. Take a look at
           HTTP::Date for recognized formats.

       -c <content-type>
           Set the Content-Type for the request.  This option is only allowed
           for requests that take a content, i.e. POST and PUT.  You can force
           methods to take content by using the "-f" option together with
           "-c".  The default Content-Type for POST is
           "application/x-www-form-urlencoded".  The default Content-type for
           the others is "text/plain".

       -p <proxy-url>
           Set the proxy to be used for the requests.  The program also loads
           proxy settings from the environment.  You can disable this with the
           "-P" option.

       -P  Don't load proxy settings from environment.

       -H <header>
           Send this HTTP header with each request. You can specify several,
           e.g.:

               lwp-request \
                   -H 'Referer: http://other.url/' \
                   -H 'Host: somehost' \
                   http://this.url/

       -C <username>:<password>
           Provide credentials for documents that are protected by Basic
           Authentication.  If the document is protected and you did not
           specify the username and password with this option, then you will
           be prompted to provide these values.

       The following options controls what is displayed by the program:

       -u  Print request method and absolute URL as requests are made.

       -U  Print request headers in addition to request method and absolute
           URL.

       -s  Print response status code.  This option is always on for HEAD
           requests.

       -S  Print response status chain. This shows redirect and authorization
           requests that are handled by the library.

       -e  Print response headers.  This option is always on for HEAD
           requests.

       -E  Print response status chain with full response headers.

       -d  Do not print the content of the response.

       -o <format>
           Process HTML content in various ways before printing it.  If the
           content type of the response is not HTML, then this option has no
           effect.  The legal format values are; "text", "ps", "links", "html"
           and "dump".

           If you specify the "text" format then the HTML will be formatted as
           plain "latin1" text.  If you specify the "ps" format then it will
           be formatted as Postscript.

           The "links" format will output all links found in the HTML
           document.  Relative links will be expanded to absolute ones.

           The "html" format will reformat the HTML code and the "dump" format
           will just dump the HTML syntax tree.

           Note that the "HTML-Tree" distribution needs to be installed for
           this option to work.  In addition the "HTML-Format" distribution
           needs to be installed for "-o text" or "-o ps" to work.

       -v  Print the version number of the program and quit.

       -h  Print usage message and quit.

       -a  Set text(ascii) mode for content input and output.  If this option
           is not used, content input and output is done in binary mode.

       Because this program is implemented using the LWP library, it will only
       support the protocols that LWP supports.

SEE ALSO
       lwp-mirror, LWP

COPYRIGHT
       Copyright 1995-1999 Gisle Aas.

       This library is free software; you can redistribute it and/or modify it
       under the same terms as Perl itself.

AUTHOR
       Gisle Aas <gisle AT aas.no>

perl v5.34.0                      2026-05-22                   LWP-REQUEST(1p)