Command Reference Guide

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1/!!!intro.1
________________________________________________________________
___ ___
e
elm(1) elm(1)
To reply, use the Message Menu r (reply) command (you cannot use the Message Menu g (group reply)
command). elm prompts you for each field, with any text present between the fields displayed as appropri-
ate. The example above is presented line-by-line; user input is in italic type:
On-Line Phone and Address Database
Please fill out and return as soon as possible.
Name:
my name
Manager:my manager
Department: my department
Division:my division
Your home address:home address
Home phone number:phone number
Thank you for your cooperation.
The received message would look like this:
On-Line Phone and Address Database
Please fill out and return as soon as possible.
Name: my name
Manager: my manager
Department: my department Division: my division
Your home address: home address
Home phone number: phone number
Thank you for your cooperation.
HEADER FILE
The $HOME/.elm/elmheaders
file provides you with a way to specify special information headers such
as
X-Organization:, X-Phone:
, and so forth. The nonblank lines from this file are added to the
headers of all outbound mail.
Entries in the
elmheaders file should have the following format:
header-name: header-string
header-name: must not contain blanks. header-string can be continued over several lines by preceding
each continuation line with blanks, as indicated by the output below.
Within the
elmheaders file, you can use backquotes (left apostrophes) to execute shell commands when
the file is read, so that an entry of the form:
X-Operating-System: ‘uname -a‘
would produce a header entry like:
X-Operating-System:
HP-UX hpulpc17 B.10.10 A 9000/710 2012505939 two-user license
According to RFC 822, user-defined header names should begin with X- or x-. Otherwise, they risk hav-
ing their usage overridden if the name is later standardized with some other meaning.
Defined Headers
The following header names are defined for the message header in RFC 822 and RFC 1521.
Bcc: (822) Cc: (822)
Comments: (822) Content-Description: (1521)
Content-ID: (1521) Content-Transfer-Encoding: (1521)
Content-Type: (1521) Date: (822)
Encrypted: (822) From: (822)
In-Reply-To: (822) Keywords: (822)
MIME-Version: (1521) Message-ID: (822)
Received: (822) References: (822)
Reply-To: (822) Resent-Bcc: (822)
Resent-Cc: (822) Resent-Date: (822)
Resent-From: (822) Resent-Message-ID: (822)
Resent-Reply-To: (822) Resent-Sender: (822)
Resent-To: (822) Return-Path: (822)
Sender: (822) Subject: (822)
To: (822) X-user-defined: (822)
HP-UX Release 11i: December 2000 − 18 − Section 1−−221
___
___