Previous | Contents | Index |
Redistribute a message.
REDISTRIBUTE
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 /DELAY_WARNING /DELAY_WARNING /DELIVERY_RECEIPT See text /FROM=address /NOFROM /IGNORE See text /MULTIPLE /SINGLE /PERSONAL_NAME=name See text /PRIORITY=priority See text /READ_RECEIPT See text /REMOVE /NOREMOVE /RETURN_CONTENT /RETURN_CONTENT /SELF See text /SENSITIVITY=sensitivity See text /SINGLE /SINGLE /SUBADDRESS None /TO /TO_PROMPT /TO_LIST=address None /TO_PROMPT /TO_PROMPT /USER=username None
None.
Either the REDISTRIBUTE or FORWARD command may be used to forward a message to other individuals. However, unlike the FORWARD command which affords you the opportunity to modify the message prior to actually forwarding it, the REDISTRIBUTE command does not allow you to modify or change the message. There is, however, an advantage to this: it allows the message to be forwarded such that a recipient of it will see in the From:, Date:, To:, Cc:, and Bcc: header lines who originally sent the message, when they originally sent it, and to whom. Your address, when you redistributed the message, and who you redistributed it to will appear in Resent-From:, Resent-Date:, Resent-To:, Resent-Cc:, and Resent-Bcc: header lines. Moreover, the message will not be encapsulated the way it is by the FORWARD command.
/ABORT
/IGNORE
The /ABORT qualifier causes the message redistribution to fail if any of the Resent-To:, Resent-Cc:, or Resent-Bcc: addresses prove to be illegal. The /IGNORE qualifier permits the redistribution 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 /ABORT or /IGNORE is specified, is to prompt you when any of the addresses is illegal. You will be given the choice of whether to cancel the redistribution or to go ahead and redistribute the message to only the legal addresses./BCC
/BCC_LIST=address[,...]
/BCC_PROMPT
/NOBCC_PROMPT
You are prompted for Bcc: (blind carbon copy) addresses only when you specify the /BCC or /BCC_PROMPT qualifier. Any Bcc: addresses which you supply appear as Resent-Bcc: addresses in the header of the redistributed message. Specifying /NOBCC_PROMPT inhibits Bcc: prompting. You may use the /BCC_LIST qualifier to specify one or more Bcc: addresses on the REDISTRIBUTE command line itself. The /BCC qualifier is an abbreviation for /BCC_PROMPT./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. Any Cc: addresses which you supply appear as Resent-Cc: addresses in the header of the redistributed message. 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 REDISTRIBUTE command line itself. The /CC qualifier is an abbreviation for /CC_PROMPT./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 redistribution, 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)./FROM=address
/NOFROM
When you specify /NOFROM, the PMDF_FROM logical is ignored and a standard Resent-From: header line containing your address is generated. When you use /FROM, the specified address is used to construct the Resent-From: header line, and your real (authenticated) address is placed in a Resent-Sender: header line./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 Resent-From: header line of your redistribution. 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 and any Priority: line already present in the message being redistributed will be removed. If, instead, you specify the /PRIORITY qualifier, 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 redistribution, 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 or have /COPY_SELF enabled for forwarding. Your address will appear in the Cc: list if you specify /SELF. The combination /ALL/REMOVE/SELF is particularly useful as it prevents your own address from appearing in both the To: and Cc: address lists./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 redistribution to be sent to yourself; your address will appear in the Resent-Cc: header line. When /NOSELF is specified, you will not receive a copy of the message unless you explicitly include your address in the Resent-To:, Resent-Cc:, or Resent-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 and any existing Sensitivity: line in the message being redistributed is removed. 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./SUBADDRESS=subaddress
Attaches a subaddress to your return address./TO
/TO_LIST=address[,...]
/TO_PROMPT (default)
/NOTO_PROMPT
By default, you are prompted for additional To: addresses when you redistribute a message. The /TO_PROMPT qualifier explicitly requests this behavior. Use the /NOTO_PROMPT qualifier if you do not want to be prompted for additional To: addresses to which to send your redistribution. You may use the /TO_LIST qualifier to specify one or more To: addresses on the REPLY command line itself. The To: addresses which you supply will appear in a Resent-To: header line in the redistributed message. The /TO qualifier is an abbreviation for /TO_PROMPT./USER=username
Redistribute the message as though you are the specified user; that is, the Resent-From: address in the reply will be that of the specified user. No Resent-Sender: header line is added. Use of this qualifier requires either WORLD privilege or the PMDF_WORLD or PMDF_WORLD_username rightslist identifier.
In the following example, the user fresnel@example.com has received a message from rex@example.com. Fresnel then redistributes this message, copying herself on the redistribution, to misha@example.com and beckett@example.com. Compare this example to that shown for the FORWARD command.
The following items of note are called out in the example above:
EMAIL> READ 2 Message MAIL 2 18-FEB-2012 08:27:45.18 Date: Thu, 18 Feb 2012 08:27:45 PDT (1) From: rex@example.com Subject: Mrochek To: fresnel@example.com Have any of you seen Mrochek recently? EMAIL> REDISTRIBUTE/SELF (2) To: misha@example.com, beckett@example.com (3) EMAIL> New mail on node EXAMPLE from IN%"fresnel@example.com" (4) EMAIL> READ/NEW Message NEWMAIL 1 18-FEB-2012 12:30:10.20 Resent-date: Thu, 18 Feb 2012 12:30:10 PDT (5) Resent-from: fresnel@example.com (6) Resent-to: misha@example.com, beckett@example.com (7) Resent-cc: fresnel@example.com (6) Date: Thu, 18 Feb 2012 08:27:45 PDT (8) From: rex@example.com Subject: Mrochek To: fresnel@example.com Have any of you seen Mrochek recently? EMAIL>
- The header of the original message from rex@example.com.
- The REDISTRIBUTE/SELF command is issued.
- The redistribution is sent to misha@example.com and beckett@example.com.
- Fresnel receives her copy of the redistribution. This copy was requested by the /SELF qualifier in .
- The date and time at which the redistribution was sent.
- The address of the individual, Fresnel, who sent this redistribution.
- The recipients of the redistribution. Since Fresnel was copied on the redistribution (/SELF), Fresnel's address also appears in the Resent-cc; header line.
- The original header message header as seen in .
Previous | Next | Contents | Index |