Normally Job Administration e-mail broadcasts will contain $email_body and $email_altbody commands to supply body text with text/plain and text/html content types respectively. Individual lines of text can also be supplied on $email_text and $email_alttext commands. This text is always pre-processed at transmit time to expand variables, which should be introduced (by default) with the accent grave character (`). In addition, if $email_options PercentXX is given, then instances of %xx inside a URL link, where xx is the hexadecimal value of the e-mail variable introducer (default %60), will be taken as equivalent to the introducer character. The "`" character inside URLs is normally replaced with "%60" by HTML editing software.
The Job Administration feature can also handle the types of document listed below as e-mail attachments for simple e-mail broadcasts. Note that no Document Converter integration is available on Plain E-Mail Broadcasts.
The system will accept any document file with a content type specified on its $job_document command. However no checks are made that the content-type matches the document file extension or type, nor whether the type is a recognized MIME type. No conversions are performed except for HTML and TIF as described below.
When using Job Administration IVR, a master TIF document can be faxed in by the originator during an IVR session, with an optional proof faxed or e-mailed back for confirmation. The $job_document command should have the keyword FAXIN in the filename parameter, along with the appropriate content type of image/tif, application/pdf, image/png, image/jpg or image/gif.
|
The content-type of text/html on a $job_document command is processed specially if the $email_options keyword HtmlExpandVars is given and the original document is also HTML. In this case the variables are expanded as the transmission is made, in the same way that body text and alternate body text are expanded (see above).
Note that unlike body text files, e-mail attachments are not cached in the transmission process, and in addition all attachments are base64 encoded. It is therefore slightly less efficient to use HTML attachments than it is to use HTML body text.
|
The content-types of application/pdf, image/png, image/jpg and image/gif are processed specially if the file type of the original document on a $job_document command is TIF. In this case the document is converted to the specified format immediately before transmission. Note that jpg and gif formats are not recommended for full-page documents; their use is principally for embedded images in MHTML mail.
|
TIF originals can be customized per-recipient by means of a graphical customization overlay. This requires the $job_document filename to be either a GCT which references an existing faxable TIF watermark file, or a GTT file.
SingleEmailDoc: If the $job_options keyword of 'SingleEmailDoc' is given, then multiple separate faxable TIF files will be e-mailed as a single document, using a GCT or GTT file supplied on a separate $fax_cover command, if present. This feature allows the recipient to receive a document which appears to consist of customized 'headed stationery' and customized 'continuation pages', and which is built from separately submitted $job_document items. The content-type of the resulting single document must be specified using the control variable SINGLE_EMAIL_CT, as one of image/tif, application/pdf, image/png, image/jpg or image/gif.
The content-types of application/pdf, image/png, image/jpg and image/gif are processed specially if the file type of the original document is TIF, GCT or GTT. In this case the document is converted to the specified format immediately before transmission. Note that jpg and gif formats are not recommended for full-page documents; their use is principally for embedded images in MHTML mail.
|
