Specify E-Mail Alternate Body Text Line

$email_alttext "text" [origin]

This command specifies one of the lines of text that is to form an alternate body for the e-mail message. The e-mail is built as a MIME message with Content-Type multipart/alternative.

The parameter on this command is used as follows:

text The text to be used to create an alternate body. Each command specifies one line of source text.
originA keyword JOBTYPE, OWNER, or SYSTEM which is used to allow separate sets of alternate body and/or text commands in Job Type, Owner and System job properties to override each other correctly. This keyword is added automatically in job instance creation and should NOT be applied manually.

The default macro-expansion character on all $email... commands is an ASCII grave accent character (`). The text is processed in the same way as a CopiaFacts cover sheet with macro-expansion of '`' variables. The expansion of variables may be suppressed by $email_options "nomacro".

The text is scanned for characters not in the ASCII character set, and if any are found the text will be encoded either as 'quoted-printable' or (if specified on $email_charset) as base64. Otherwise the file will be sent as 'us-ascii' with 7bit encoding. This processing may be modified by the options specified on an $email_options command.

The $email_alttext and $email_altbody commands can be mixed in the same FS file and the alternate body text will be built from lines and files in the order they are specified.

When the email derives from the job administration system, if any alternate text and body commands originate from the Job Type properties, those originating in Owner and System properties will be ignored, and if any originate from Owner properties, those originating from System properties will be ignored.

The content type will be set to text/plain unless a string <html is detected in the first three lines of text, in which case it will be set to text/html.

CopiaFacts always places the body before the altbody in the message.  To conform with RFC2046 section 5.1.4 it is strongly recommended that when both plain and html text are present, the $email_text/$email_body commands are used for the text/plain part and the $email_alttext/$email_alt_body commands are used for the text/html part.

Default: no alternate message body is included

Positional Requirements: must not be in an FS file without either an $email_body command or an $email_text command

Example:

$email_alttext "Message text"