PMDF User's Guide
OpenVMS Edition


Previous Next Contents Index


SEND

Send a mail message.

Syntax

SEND [file-spec[,...]]

Qualifiers Defaults
/ABORT See text
/BCC /NOBCC_PROMPT
/BCC_LIST=address None
/BCC_PROMPT /NOBCC_PROMPT
/CC See text
/CC_LIST=address None
/CC_PROMPT See text
/COMMENTS See text
/CONFIRM /NOCONFIRM
/DELAY_WARNING /DELAY_WARNING
/DELIVERY_RECEIPT See text
/DIGEST See text
/EDIT /NOEDIT
/ENCAPSULATE /ENCAPSULATE
/FROM=address /NOFROM
/IGNORE See text
/INSERT See text
/LAST /NOLAST
/MULTIPLE /SINGLE
/PERSONAL_NAME=name See text
/PRIORITY=priority See text
/READ_RECEIPT See text
/REMOVE /NOREMOVE
/REPLY_TO=address See text
/RETURN_CONTENT /RETURN_CONTENT
/SELF See text
/SENSITIVITY=sensitivity See text
/SINGLE /SINGLE
/SIGNATURE=text See text
/SUBADDRESS None
/SUBJECT=subject See text
/TO /TO_PROMPT
/TO_LIST=address None
/TO_PROMPT /TO_PROMPT
/USER=username None
Positional Qualifiers Defaults
/BLOCK /TEXT
/EIGHTBIT=option /EIGHTBIT=LEAVE
/ENCODING=encoding None
/FILENAME=name /NOFILENAME
/RECORD /TEXT
/TEXT /TEXT

Parameters

file-spec[,...]

Optional list of one or more files to send. If /INSERT is specified, then these files will be sent as attachments to a message which you input from the keyboard.

Description

The SEND command originates a mail message to one or more recipients. If you supply one or more file names, then those files will be sent as the message. If in addition to supplying file names, you specify the /INSERT qualifier, then the files will be sent as attachments to a message which you enter from the keyboard.

Normally, you will just be prompted for a list of To: recipients and a Subject: line. Use the /CC or /BCC if you wish to also be prompted for Cc: (carbon copy) or Bcc: (blind carbon copy) recipients. If you have previously issued the SET CC_PROMPT command, then you will be automatically prompted for Cc: recipients.

After you have entered both the addresses of the recipients and the subject line, you are prompted to enter the message. After you have composed the message, type CTRL/Z. When CTRL/Z is entered, the message is sent; no other action is required by you. If you used the /EDIT qualifier, then your editor will be invoked and you can compose the message from within the editor. After composing the message, save it, and then exit the editor. Upon exiting the editor, the message is sent.

To abort a message send, enter CTRL/C. If you are entering the message from an editor then, to abort the send, exit the editor without saving your message.


Qualifiers

/ABORT

/IGNORE

The /ABORT qualifier causes the message send to fail if any of the To:, Cc:, or Bcc: addresses prove to be illegal. The /IGNORE qualifier permits the message to be sent provided that at least one of the addresses is legal. The illegal addresses are ignored and will not appear in the message's header. The default behavior, if neither the /ABORT or /IGNORE qualifier is specified, is to prompt you if any of the addresses are illegal. You will be given the choice of whether to cancel the send or to go ahead and send the message to just the legal addresses.

/BCC

/BCC_LIST=address[,...]

/BCC_PROMPT

/NOBCC_PROMPT

By default, you are prompted for Bcc: (blind carbon copy) addresses only when you specify either the /BCC or /BCC_PROMPT qualifier. If you specify /BCC_PROMPT, you will be presented with a "Bcc:" prompt to which you may specify zero or more Bcc: addresses. Specifying /NOBCC_PROMPT inhibits Bcc: prompting. You may use the /BCC_LIST qualifier to specify one or more Bcc: addresses in the SEND command line itself. The /BCC qualifier is an abbreviation for /BCC_PROMPT.

/COMMENTS=comment

/NOCOMMENTS

Normally, a Comments: header line is generated only when you have defined the PMDF_COMMENTS logical. If you specify /NOCOMMENTS, then that logical will not be used and no Comments: line will be added to the message. If, instead, you specify a comment with the /COMMENTS qualifier, then that comment will be placed on a Comments: header line, and PMDF_COMMENTS, if defined, will be ignored.

/CC

/CC_LIST=address[,...]

/CC_PROMPT

/NOCC_PROMPT

By default, you are prompted for Cc: (carbon copy) addresses only when you have previously used the SET CC_PROMPT command. The /CC_LIST, /CC_PROMPT, and /NOCC_PROMPT qualifiers override this behavior. If you specify the /CC_PROMPT qualifier, you will be presented with a Cc: prompt to which you may specify zero or more Cc: addresses. Specifying /NOCC_PROMPT inhibits Cc: prompting. You may use the /CC_LIST qualifier to specify one or more Cc: addresses on the SEND command line itself. The /CC qualifier is an abbreviation for /CC_PROMPT.

/CONFIRM

/NOCONFIRM (default)

When /CONFIRM is specified, you will be prompted to confirm the inclusion of each selected message in the message digest.

/DELAY_WARNING (default)

/NODELAY_WARNING

The qualifier controls whether or not PMDF requests that delay notifications be sent in case this message is not delivered immediately. The default is that PMDF requests delay notifications. However, note that some remote mailers may not support sender specification of whether delay notifications be sent and may unconditionally do one or the other regardless of whatever you request.

/DELIVERY_RECEIPT[=keyword]

/NODELIVERY_RECEIPT

Normally, a Delivery-receipt-to: header line is generated only when you have defined the PMDF_DELIVERY_RECEIPT logical. If you specify /NODELIVERY_RECEIPT, then no Delivery-receipt-to: line will be generated. If, instead, you specify the /DELIVERY_RECEIPT qualifier, then a delivery receipt will be requested of all recipients of the message, and the PMDF_DELIVERY_RECEIPT logical, if defined, will be ignored. One of the keywords HEADER, NOTARY, or BOTH may optionally be specified to control what style of delivery receipt to construct (header style, NOTARY envelope style, or both, respectively).

/DIGEST=number[,...]

/NODIGEST (default)

Send the specified messages as a MIME message digest. One or more messages may be specified via their message numbers. Ranges are permitted: /DIGEST=(1,3,6-9,15-20) specifies messages 1, 3, 6 through 9, and 15 through 20.

/EDIT[=option]

/NOEDIT (default)

To compose your message from within an editor, specify the /EDIT qualifier. The /NOEDIT qualifier prevents an editor from being invoked. By default, an editor is only invoked if, when you ran PMDF MAIL, you specified the qualifier /EDIT=(SEND). By default the message's RFC 822 header will also appear in the editor. To suppress the presentation of the RFC 822 header, specify /EDIT=NOHEADER. To request that the header appear in the editor, specify /EDIT=HEADER.

/ENCAPSULATE (default)

/NOENCAPSULATE

Specify whether or not to treat input files specified with the optional file-spec parameter as separate attachments each encapsulated as a separate message body part.

/FROM=address

/NOFROM

When you specify /NOFROM, the PMDF_FROM logical is ignored and a standard From: header line containing your address is generated. When you use /FROM, the specified address is then used to construct the From: header line, and your real (authenticated) address is placed in a Sender: header line.

/INSERT

/NOINSERT

The /INSERT qualifier instructs PMDF MAIL to prompt you for additional message text and insert it as an attachment to the message. The additional text, which is composed by hand either through an editor or in response to the "Enter your message below" prompt, appears at the top of the message with any attached files appended afterwards.

/LAST

/NOLAST (default)

The /LAST qualifier causes the content of the last message you sent to be used as the content for this message; i.e., resends the previous message. /NOLAST selects the default behavior in which you are expected to generate the content of the message yourself.

/MULTIPLE

/SINGLE (default)

By default, you are prompted only once for each type of recipient address, To:, Cc:, and Bcc:. If you specify /MULTIPLE, then you will be prompted repeatedly for each of these address types. For each type, the prompt will repeat until you enter a blank line. /SINGLE selects the default behavior.

/PERSONAL_NAME=name

/NOPERSONAL_NAME

The /PERSONAL_NAME and /NOPERSONAL_NAME qualifiers override the setting of the SET PERSONAL_NAME command. When you use the /PERSONAL_NAME qualifier, then the specified name will be used in the personal name field of your return address which appears in the From: header line of your message. Specifying /NOPERSONAL_NAME prevents any personal name from appearing in your return address.

/PRIORITY=priority

/NOPRIORITY

Normally, a Priority: header line is generated only when you have defined the PMDF_PRIORITY logical. If you specify /NOPRIORITY, then no Priority: line will be generated. If, instead, you specify the /PRIORITY qualifier, then the supplied priority will be included in a Priority: header line. The legal priorities are: NO-PRIORITY, THIRD-CLASS, SECOND-CLASS, NON-URGENT, NORMAL, and URGENT. NO-PRIORITY is equivalent to /NOPRIORITY.

/READ_RECEIPT

/NOREAD_RECEIPT

Normally, a Read-receipt-to: header line is generated only when you have defined the PMDF_READ_RECEIPT logical. If you specify /NOREAD_RECEIPT, then no Read-receipt-to: line will be generated. If, instead, you specify the /READ_RECEIPT qualifier, then a read receipt will be requested of all recipients of the message, and any address specified by the PMDF_READ_RECEIPT logical will be ignored.

/REMOVE

/NOREMOVE (default)

When /REMOVE is specified, your address will be removed from the list of recipients even if you explicitly specified your address as a To:, Cc:, or Bcc: address list or have /COPY_SELF enabled for sending. Your address will appear in the Cc: list if you specify /SELF.

/REPLY_TO=address

/NOREPLY_TO

Normally, a Reply-to: header line is generated only when you have defined the PMDF_REPLY_TO logical. If you specify /NOREPLY_TO, then no Reply-to: line will be generated. If, instead, you specify the /REPLY_TO qualifier, then the supplied address will be placed in a Reply-to: header line, and any PMDF_REPLY_TO logical ignored.

/RETURN_CONTENT (default)

/NORETURN_CONTENT

These qualifiers control whether return-of-content is requested for non-delivery reports.

/SELF

/NOSELF

The /SELF and /NOSELF qualifiers override the behavior of the SET COPY_SELF command. /SELF causes a copy of your message to be sent to you; your address will appear in the Cc: header line. When /NOSELF is specified, you will not receive a copy of the message unless you explicitly include your address in the To:, Cc:, or Bcc: address lists.

/SENSITIVITY=sensitivity

/NOSENSITIVITY

Normally, a Sensitivity: header line is generated only when you have defined the PMDF_SENSITIVITY logical. If you specify /NOSENSITIVITY, then no Sensitivity: line will be generated. If, instead, you specify the /SENSITIVITY qualifier, then the supplied sensitivity will be included in a Sensitivity: header line. The legal sensitivities are: NOT-SENSITIVE, PERSONAL, PRIVATE, and COMPANY-CONFIDENTIAL. NOT-SENSITIVE is equivalent to /NOSENSITIVITY.

/SIGNATURE=signature-spec

/NOSIGNATURE

Normally, signature lines are appended to the end of your message only if the PMDF_SIGNATURE logical is defined. When you specify /NOSIGNATURE, no signature lines are appended to your message. When, however, you specify the /SIGNATURE qualifier, then the specified signature is appended to your message. If signature-spec begins with an at-sign, @, then the signature lines are copied from the file name following the at-sign; otherwise, signature-spec itself is appended to the end of the message.

/SUBADDRESS=subaddress

Attaches a subaddress to your return address.

/SUBJECT=subject

/NOSUBJECT

By default, you will be prompted to supply a Subject: line. /NOSUBJECT suppresses this prompt; no Subject: line will appear in the message. To specify a subject on the SEND command line, use the /SUBJECT qualifier.

/TO

/TO_LIST=address[,...]

/TO_PROMPT (default)

/NOTO_PROMPT

By default, you are prompted for the To: addresses to which to send the message. The /NOTO_PROMPT qualifier suppresses this prompting. You may use the /TO_LIST qualifier to specify one or more To: addresses on the SEND command line itself. The /TO qualifier is an abbreviation for /TO_PROMPT.

/USER=username

Send the message as though you are the specified user; that is, the From: address in the message will be that of the specified user. No Sender: header line is added. Use of this qualifier requires either WORLD privilege or the PMDF_WORLD or PMDF_WORLD_username rightslist identifier. The /USER qualifier is intended for use by postmasters. It comes in handy when you need to unsubscribe a user from a remote mailing list. WORLD privilege is required to use this qualifier. /NOPERSONAL_NAME is implied when /USER is specified.


Positional Qualifiers

/BLOCK

/RECORD

/TEXT

The /BLOCK, /RECORD, and /TEXT positional qualifiers may only be used in conjunction with an input file specification. These qualifiers allow you to override the default file reading (access) mode which PMDF would otherwise use to read the input file. Typically, PMDF uses /TEXT.

/EIGHTBIT=option

/NOEIGHTBIT

Specify how to handle eight bit characters in an input file (i.e., characters for which the eighth bit is set). The available options are:
HEXIFY Replace each eight bit character with =XX where "XX" is the character's ordinal value expressed in hexadecimal.
LEAVE Leave eight bit characters untouched. This is the default behavior.
REMOVE Remove eight bit characters from the message; removed characters are not replaced with anything to indicate their removal or former presence.
REPLACE Replace each eight bit character with a question mark, "?".
STRIP Clear the eighth bit in each character of the message; i.e., "strip" the eighth bit from eight bit characters.
The default behavior is /EIGHTBIT=LEAVE. Use /NOEIGHTBIT or /EIGHTBIT=REMOVE to remove all eight bit characters from input files.

/ENCODING=encoding

The /ENCODING positional qualifier may only be used in conjunction with an input file specification. The /ENCODING qualifier allows you to override the default file encoding method which PMDF would otherwise use to encode the input file. The legal encoding types are: NONE, 8BIT, 7BIT, BASE32, BASE64, BASE85, BINHEX, BTOA, HEXADECIMAL, OLD-BASE64 (for use with PMDF V4.0), PATHWORKS, QUOTED-PRINTABLE, UUENCODE, COMPRESSED-BASE64, and COMPRESSED-UUENCODE.

/FILENAME=name

/NOFILENAME (default)

The /FILENAME and /NOFILENAME positional qualifiers may only be used in conjunction with an input file specification. When an input file is attached as a separate message body part, that part's Content-type: header line will, by default, omit the optional file name parameter. This default behavior is explicitly selected with the /NOFILENAME qualifier. When /FILENAME is specified, the name of the input file will be included in the Content-type: header line. If no value is specified on the /FILENAME qualifier, then the name of the input file is used.

Examples

#1

EMAIL> SEND
To: Mrochek
Subject: Weekly staff meeting?
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
Did I hear correctly that the weekly staff meeting is cancelled this week?
 
Fresnel
[CTRL/Z]
EMAIL>
      

In this example, a simple message is sent to Mrochek.

#2

EMAIL> SEND/CC
To: Mrochek
Cc: Beckett, Misha@example.com, Rex@example.com
Subject: Weekly staff meeting?
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
Did I hear correctly that the weekly staff meeting is cancelled this week?
 
Fresnel
 
P.S. I copied Beckett, Misha, and Rex on this message since
     they're confused too.
[CTRL/Z]
EMAIL>
      

Here, a message is sent to Mrochek. Beckett, Misha@example.com, and Rex@example.com are also copied on the message; they will each receive a copy of the message and their addresses will appear in a Cc: header line.

#3

EMAIL> SEND/BCC
To: Mrochek
Bcc: Beckett
Subject: Weekly staff meeting?
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
Did I hear correctly that the weekly staff meeting is cancelled this week?
 
Fresnel
[CTRL/Z]
EMAIL>
      

In this example, the /BCC qualifier is used and Beckett is specified as a Bcc: recipient. This means that Beckett will receive a copy of the message. However, Mrochek's copy will not indicate this; that is, Beckett's address will not appear in the copy of the message sent to Mrochek.

#4

EMAIL> SEND/EDIT
To: Mrochek
Subject: Weekly staff meeting?
[the editor is invoked]
[compose your message]
[save the message]
[exit the editor]
EMAIL>
      

This sample shows how to invoke the editor and compose your message from within it.

#5

EMAIL> SEND/EDIT/LAST
To: Beckett
Subject: Weekly staff meeting?
[the editor is invoked]
[edit the previous message]
[save the edited message]
[exit the editor]
EMAIL>
      

This sample shows how to resend your last message after first editing it.

#6

EMAIL> SEND LETTER.TXT
To: Rex@example.com
Subject: Greetings
EMAIL>
      

Here, the contents of the file LETTER.TXT are sent as a message to Rex@example.com.

#7

EMAIL> SEND/INSERT BONE.DAT
To: Misha@example.com
Subject: Best bones
Enter your message below. Press CTRL/Z when complete, or CTRL/C to quit:
Misha,
Attached below, please find my summary compilation on the best bone buys
in town.
                            Mrochek
[CTRL/Z]
EMAIL>
      

In this example, a message with a file attachment is sent to Misha@example.com. The file BONE.DAT is attached to the input text and the two sent as a single message to Misha@example.com.


Previous Next Contents Index