Creating an email header
You can include an email header in line-data documents to specify the addresses of the email recipients and the subject of the email. Infoprint Server supports a subset of the fields defined in the RFC 2822 Internet Message Format standard. Other fields are ignored.
Table 1 shows the supported fields and values in an email header.
Field name | Value |
---|---|
to | A list of 1 - 32 email addresses for the recipients
of the email. Each email address can be 1 - 60 characters but cannot
include blanks. Separate email addresses with one or more blanks,
a comma, or both. Example: to:
user1@xyz.com, user2@xyz.com, dept01list
|
cc | A list of 1 - 32 email addresses of the copy
(cc) recipients of the email. A cc means that other recipients
of the email can see the cc recipient listed. Each email address can
be 1 - 60 characters but cannot include blanks. Separate email addresses
with one or more blanks, a comma, or both. Example: cc: user3@xyz.com, user4@xyz.com
|
bcc | A list of 1 - 32 email addresses of the blind
copy (bcc) recipients of an email. A bcc means that other
recipients of the email do not see the bcc recipient listed. Each
email address can be 1 - 60 characters but cannot include blanks.
Separate email addresses with one or more blanks, a comma, or both. Example: bcc: user5@xyz.com, user6@xyz.com
|
from | The descriptive name of the sender of the email.
The name can be 1 - 60 characters and can include blanks. Infoprint Server includes the descriptive name before the sender's actual email address: userid@domainname. The userid is the user ID of the job submitter, and domainname is the domain name where Infoprint Server is running. Example: This
specification in the from field in the header:
Puts
this information in the email:
|
reply-to | The email address that recipients of the email
can reply to. The email address can be 1 - 60 characters but cannot
include blanks. If none is specified, the reply address is userid@domainname.
The userid is the user ID of the job submitter,
and domainname is the domain name where Infoprint Server
is running. Example: reply-to:
sender@xyz.com
|
subject | The subject of the email. The subject can be
1 - 60 characters and can include blanks. Example: subject: Annual Report
|
The email header fields must be in this format:
field name : value
- field name
- Table 1 shows the supported field names. Other fields are allowed but ignored. The field names can include lowercase or uppercase characters. If a field name occurs more than one time, the last one is used.
- :
- The colon separates the field name from the value. Blanks are allowed before and after the colon.
- value
- Table 1 shows the allowed values. Infoprint Server uses z/OS® UNIX sendmail, so the email addresses must be in a format that sendmail supports. An email address can be an alias name that is defined to sendmail. The email address cannot contain blanks.
Requirements:
- The output data set on the spool must contain line data in EBCDIC representation, with or without carriage controls.
- The Embedded headers field in the printer definition must be selected, or you must specify the mail-embedded-headers=yes job attribute.
Limitations: Email headers are not supported
in these situations:
- Your installation runs IP PrintWay™ basic mode instead of extended mode.
- You submit the print request with the z/OS UNIX lp command, the Print Interface subsystem, the Infoprint Port Monitor, or another remote print submission method.
Syntax rules:
- Include an email header field name and colon in the first record.
- Include at least one of the fields that Infoprint Server supports in the header.
- Begin each field in data column 1 of the record after the carriage control (if any).
- To continue a field on the next record, continue the value in column 2 or after.
- Do not split an email address across records.
- End the header in the first 32 records. A blank record indicates the end of the header.
- To include comments, use the comment field. Comments in parentheses are considered text.
Tips:
- If there is no text after the email header, specify the mail-inline-text job attribute to avoid an empty email attachment. Or, the administrator can select the Inline text and line data field in the printer definition.
- To send multiple documents in the same print job to different email addresses, the administrator must specify the AOP_MAIL_USE_FIRST_ADDRESS = NO environment variable or the mail-use-first-address=no configuration attribute.
- You can include email headers in VTAM® application data that you send to the NetSpool component of Infoprint Server. Specify each email header field on a new line in the VTAM application data and end the header with a blank line.
The email header fields override the corresponding Infoprint Server
job attributes, JCL parameters, and printer definition fields that
are shown in Table 2.
If a field is not specified in the email header, Infoprint Server
uses the value in the corresponding job attribute, JCL parameter,
or printer definition (in that order).
Email header field | Job attribute | Parameter on OUTPUT JCL statement | Printer definition field |
---|---|---|---|
to | mail-to-addresses | MAILTO | To addresses |
cc | mail-cc-addresses | MAILCC | CC addresses |
bcc | mail-bcc-addresses | MAILBCC | BCC addresses |
from | mail-from-name | MAILFROM | From name |
reply-to | mail-reply-name | REPLYTO | Reply address |
subject | title-text | TITLE | Title |