Guidelines for Naming Enhanced Lists
Table
| Field Name | Description/Procedure | |
|
|
|
|
| DEFAULT | Enter the number of the COS assigned to the | |
| MAILBOX ATTRIBUTES | mailbox and the shadow mailbox. | |
| Class of Service: | ELA uses this COS number when you create new enhanced lists. | |
|
| ||
| Valid Input: |
|
|
| a number from 2 to 11 |
|
|
|
|
|
|
| DEFAULT | Enter the number of the community assigned to the | |
| MAILBOX ATTRIBUTES | ||
| Community ID: | shadow mailbox Community ID. | |
| Valid Input: | The | |
| a number from 1 to 15 | be able to send messages to all other communities and receive | |
| messages from the community(ies) containing users with access | ||
|
| ||
|
| to enhanced lists. See "Setting Up ELA and Shadow Mailbox | |
|
| Community IDs" on page | |
|
|
|
|
|
|
|
|
Continued on next page
3.Press (F3) SAVE to save the ELA server information to the system database.
The system displays the message “Successfully Updated!” and asks you to press F1 acknowledge the message.
4.Press (F1) ACKNOWLG MESSAGE .
The system redisplays the Enhanced List Manager menu.
5.Continue with the next procedure or press (F6) CANCEL repeatedly to return to the main menu.
Guidelines for Naming Enhanced Lists
We recommend that you use the following guidelines when you name an enhanced list. These guidelines can help prevent users from inadvertently sending their messages to the enhanced list, instead of to a person.
■Do not use embedded spaces in the called Marketing Department, type it
name. If you would like a list to be Marketing_Department_LIst.
■Avoid naming an enhanced list after a person. INTUITY Message Manager does not differentiate between an enhanced list and a person’s name.
Examples of names to avoid:
—Jane_Doe
—Doe_Jane
Issue 1 July 1997 37