Before running EMAIL, your e-mail address must be established in either the EMAIL attribute of your USERDATA record or in your CANDE/MYOPTIONS file.

The <usercode> form of an <address> can be used only if that user's USERDATA record contains the EMAIL address.

You can initiate the EMAIL utility by any of the following methods:

CANDE/MYOPTIONS

Records in your CANDE/MYOPTIONS file can define your name and e-mail address, override organizational components of a news article's organization, set default options, and define alias address lists. EMAIL recognizes records within your CANDE/MYOPTIONS file that begin with “*” or EMAIL.

The *NAME and *EMAIL address can be used to establish your name and e-mail address overriding your identity and e-mail attributes in your USERDATA record by using the following format:

*NAME=My Name
*EMAIL=Myron.Namemycompany.com

If you submit a news article, EMAIL uses *COMPANY, *DEPARTMENT, and *BUILDING records in your CANDE/MYOPTIONS file or in the *INSTALLATION/OPTIONS file to build the ORGANIZATION header. For example:

*DEPARTMENT=My Department

You can use the EMAIL: record to define options to be used every time you run EMAIL. For example:

EMAIL: WRAP OFF

You can use an EMAIL MAIL: and EMAIL NEWS: record to define options to be used every time you send an e-mail and submit a news article, respectively, as shown below:

EMAIL MAIL: BCC
EMAIL NEWS: EXPIRES=31 

You can also specify the login authentication in your CANDE/MYOPTIONS file by using the LOGIN option in the default MAIL option as in the following example:

EMAIL MAIL: BCC, LOGIN=”myusercode”/”mypassword”

You can define an address alias, for an individual or group, using the following syntax:

── EMAIL ──<alias>── = ──<addr list>───────────────────────────────────┤

For example:

EMAIL ERIK=ErikJones@hiscompany.com
EMAIL ETEAM=#ERIK, “Mark Smith” MarkSmith@ivyleague.edu
EMAIL SUPPORT=My.Contact@unisys.com 

Files

The files BODY, SIGNATURE, and XHEADERS can be file equated to include the body, signature, and nonstandard (X-token) headers of the message, respectively.