post(8) [osf1 man page]
post(8) System Manager's Manual post(8) NAME
post - deliver a message SYNOPSIS
/usr/lib/mh/post [options] file OPTIONS
Specifies a file that post should take aliases from. More than one file can be specified, each being preceded with the -alias option. The post program automatically consults the system alias file, /usr/lib/mh/MailAliases. If there is an Aliasfile entry in your post also con- sults the file named in that entry. Filters (re-formats) messages sent to blind copy recipients. Recipients named in the Bcc: field nor- mally receive a new message which includes a copy of the message sent to the other recipients. If this option is specified, this copy of the message is filtered according to the instructions in the named file. The default is -nofilter. Formats messages so as to conform to ARPAnet Internet Message Format protocol. This is the default behavior. You can post from formatting messages in this way by using the -noformat option. Prints a list of the valid options to this command. Adds a Message-ID: or Resent-Message-ID: field to the header. Specifies the mail system over which mail is sent. The only value allowed is smtp, which is the standard mail system. Additional values are supported only for use with other mail systems. Informs the user of each step of the posting/filing process. Allows the user to watch the transport system's handling of the message (for example, local and fast delivery). Specifies the preferred length of the header compo- nents that contain addresses. The default settings for post are: -alias /usr/lib/mh/MailAliases -format -nomsgid -mts smtp -noverbose -nowatch -width 72 -nofilter DESCRIPTION
The program post is called by send(1) to deliver the message in the named file to local and remote users. In fact, all of the functions at- tributed to send on its reference page are performed by post, with send acting as a relatively simple pre-processor. Thus, it is post which parses the various header fields, appends From: and Date: lines, and interacts with the transport system. Normally, post would not be called directly by the user. It searches the To:, cc:, Bcc:, 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 option is set). This will normally cause @local-site to be appended to each local destination address, as well as any local return addresses. If a Bcc: field is encountered, the mail system will use its addresses for delivery. The Bcc: is removed from the message sent to original recipients. The copied recipients will receive an entirely new message with a minimal set of headers. The mail system includes a copy of the message sent to the original recipients in the body of the message. This command consults the environment variable $SIGNATURE to determine the sender's personal name in constructing the From: line of the message. RESTRICTIONS
For this version, the -mts option only supports the value smtp. Additional values are supported for use only with other mail systems. PROFILE COMPONENTS
The post command does not consult the user's FILES
The system customization file. The program to process Fcc:s. The program to process Bcc:s. The system alias file. SEE ALSO
Commands: comp(1), mhmail(1), send(1) Files: mh-alias(4), mh-mail(4), mtstailor(4) Standard for the Format of ARPA Internet Text Messages (RFC 822) post(8)
Check Out this Related Man Page
POST(8) [nmh-1.5] POST(8) NAME
post - deliver a message SYNOPSIS
/usr/lib/mh/post [-alias aliasfile] [-filter filterfile] [-nofilter] [-format | -noformat] [-mime | -nomime] [-msgid | -nomsgid] [-verbose | -noverbose] [-watch | -nowatch] [-width columns] [-server servername] [-port portname/number] [-sasl] [-nosasl] [-saslmaxssf ssf] [-saslmech mechanism] [-user username] [-tls] [-notls] file [-version] [-help] 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. 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 local 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 delivery, 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. Included in the body of the message will be a copy of the message sent to the sighted recipients. If -filter filterfile is specified, then this copy is filtered (re-formatted) by mhl prior to being sent to the blind recipients. Alternately, if the -mime switch is given, then post will use the MIME rules for encapsulation. The -alias aliasfile switch can be used to specify a file that post should take aliases from. More than one file can be specified, each being preceded with -alias. In any event, the primary alias file is read first. The -msgid switch indicates that a "Message-ID:" or "Resent-Message-ID:" field should be added to the header. 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" deliv- ery). Under normal circumstances, post uses the "From:" line in the message draft as the identity of the the originating mailbox. A "From:" line is required in all message draft. By default the message composition utilities such as comp and repl 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 submit- ting the message to the mail transport system. This will override both the value of the "From:" line and a "Sender:" line (if one is sup- plied). 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 transport systems support this feature. If nmh is using the SMTP MTA, the -server and the -port switches can be used to override the default mail server (defined by the servers entry in /etc/nmh/mts.conf ). 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). -saslmech switch can be used to select a particular SASL mechanism, and the the -user switch can be used to select a authorization userid to provide to SASL other than the default. 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 transaction with the -snoop switch. The -saslmaxssf switch can be used to select the maximum value of the Security Strength Factor. This is an integer value and the exact meaning of this value depends on the underlying SASL mechanism. A value of 0 disables encryption. If nmh has been compiled with TLS support, the -tls and -notls switches will require and disable the negotiation of TLS support when con- necting to the SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and `(tls-decrypted)' when viewing the SMTP transction with the -snoop switch. 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-tailor(5), Standard for the Format of ARPA Internet Text Messages (RFC-822) DEFAULTS
`-alias' defaults to /etc/nmh/MailAliases `-format' `-nomime' `-nomsgid' `-noverbose' `-nowatch' `-width 72' `-nofilter' CONTEXT
None BUGS
"Reply-To:" fields are allowed to have groups in them according to the 822 specification, but post won't let you use them. MH.6.8 11 June 2012 POST(8)