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 13 shows the supported fields and values in an email header.

from: John Q. Sender

From: John Q. Sender <JOHN@SYSTEM1>

The email header fields must be in this format:

field name : value

field name

Table 13 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 13 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 using the z/OS UNIX lp command, the Print Interface subsystem, the Infoprint Port Monitor, or another remote print submission method.

In these situations, the header is included as text in the email or in an attachment. Email addresses in the headers are not used.

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:

1. 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.
2. 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.
3. 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 shown in Table 14. 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).