Lucent Technologies INTUITY Messaging Solutions Manual
Lucent Technologies INTUITY Messaging Solutions Manual

Lucent Technologies INTUITY Messaging Solutions Manual

Enhanced-list application release 1.0
Table of Contents

Advertisement

Quick Links

I
™ Messaging Solutions
NTUITY
Enhanced-List Application
Release 1.0
585-310-575
Comcode 107975674
Issue 1
July 1997

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the INTUITY Messaging Solutions and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Lucent Technologies INTUITY Messaging Solutions

  • Page 1 ™ Messaging Solutions NTUITY Enhanced-List Application Release 1.0 585-310-575 Comcode 107975674 Issue 1 July 1997...
  • Page 2 Issue 1, July 1997 taken to reduce that risk. Lucent Technologies does not warrant that For additional documents, refer to the section in “About This Docu- this product is immune from or will prevent unauthorized use of com- ment”...
  • Page 3: Table Of Contents

    Contents About This Book Purpose Intended Audiences Trademarks and Service Marks Related Resources viii How to Comment on This Book viii Enhanced-List Application Overview Audience What You Should Know Enhanced-List Application What ELA Can Do for You ELA Administration Basic Concepts Planning with Professional Services Things to Consider Installation...
  • Page 4 Contents Increasing the Number of Mailing Lists Allowed on the System Defining an ELA Class of Service Setting Up ELA and Shadow Mailbox Community IDs Things to Consider Before You Begin ELA Community ID Shadow Mailbox Community ID Administering TCP/IP Before You Begin Setting Up IMAPI Sessions for Trusted Server Access...
  • Page 5 Contents Checking the Administrator’s Log Checking the Delivery Failure Log Delivery Failure Codes Troubleshooting ELA Alarms Overview DELIVTS Resource Type REGISTRY Resource Type SHADOW Resource Type EL — Enhanced-List Application Index Issue 1 July 1997...
  • Page 6 Contents Issue 1 July 1997...
  • Page 7: About This Book

    About This Book Purpose This book contains instructions for installing and administrating the ® Enhanced-List Application (ELA) on an I ™ AUDIX R4 system. NTUITY Intended Audiences This book is intended primarily for the on-site technical personnel who are responsible for installing and configuring the system and performing initial administration and acceptance testing.
  • Page 8: Trademarks And Service Marks

    The following trademarked products are mentioned in books in the Lucent I NTUITY document set: AT™ is a trademark of Hayes Microcomputer Products, Inc. ® AUDIX is a registered trademark of Lucent Technologies™. ® cc:Mail is a registered trademark of cc:Mail, a subsidiary of Lotus Development Corporation. ®...
  • Page 9 Trademarks and Service Marks ® Novell is a registered trademark of Novell, Inc. ® Paradyne is a registered trademark of Lucent Technologies™. ® Phillips is a registered trademark of Phillips Screw Company. ® Rolm is a registered trademark of International Business Machines.
  • Page 10: Related Resources

    We are always interested in your suggestions for improving this book. Please complete and return the reader comment card that is located behind the title page. If the reader comment card has been removed, send your comments to: Lucent Technologies Product Documentation Room 22-2H15 11900 North Pecos Street...
  • Page 11: Overview

    Enhanced-List Application Overview This chapter describes the Enhanced-List Application (ELA) on an I ™ NTUITY ® AUDIX Release 4 system. Audience Read this book if you are the AUDIX system administrator responsible for the configuration and maintenance of an I AUDIX Release 4 system.
  • Page 12: Enhanced-List Application

    Enhanced-List Application Enhanced-List Application The Enhanced-List Application (ELA) greatly expands your business’ capability to deliver messages to large numbers of recipients. A single enhanced list can contain 1500 addresses and you – the system administrator – can create up to 100 such lists.
  • Page 13: Ela Administration

    ELA Administration Forward messages to support staff automatically. If you often forward incoming messages, you can create an enhanced-list mailbox that automatically forwards messages to your staff. Your staff can review the messages and then respond to them as they normally would. ELA Administration Only the system administrator (sa) login can administer enhanced lists.
  • Page 14: Things To Consider

    Enhanced-List Application This administration can be divided as follows: AUDIX Administration: Contact Professional Services (or your account representative, if you did not contract with Professional Services) to have ELA installed. Contact Professional Services (or your account representative, if you did not contract with Professional Services) to have ELA activated.
  • Page 15 ELA Administration Hardware/Software Requirements ELA runs on the same machine as AUDIX. ELA must be installed on a Lucent I R4.2-4 or higher machine. If NTUITY your site has an earlier release, contact your Lucent service representative to obtain the necessary upgrade. ELA is not available for pre-R4 Lucent systems.
  • Page 16 Enhanced-List Application Port Usage Impact Voice port usage increases as recipients retrieve messages sent by ELA. Plan for the increase with Professional Services when you purchase ELA. Refer to the worksheets that were compiled at the time of the purchase to determine the port usage impact.
  • Page 17 ELA Administration The IMAPI password is an optional, secondary level of security used to prevent an unauthorized source external to AUDIX from starting an IMAPI session. We strongly recommend that you take advantage of this extra protection. If you choose to administer an IMAPI password, we recommend that you change it on a regular basis, for example, monthly.
  • Page 18 Enhanced-List Application cannot be infected with viruses embedded in these software files, client machines may become infected when a user launches the application associated with the software file. CAUTION: ELA does not perform any virus detection. Your company should evaluate the security risks of file attachments carefully and make provisions for virus detection software on PCs running Message Manager or an e-mail application supported by I...
  • Page 19: Installation

    Installation Overview This chapter describes how to install ELA on a Lucent I R4.2 or higher NTUITY system. Installing the Software The ELA package is provided on a tape labeled Enhanced-List Application . To install ELA on a Lucent I R4.2 or higher system: NTUITY 1.
  • Page 20 Installation Figure 2-1. Software Install Menu 3. Insert the tape labeled Enhanced-List Application into the tape drive. 4. Select: > Tape drive The system displays the message: Insert a tape into the Tape Drive. Type [go] when ready or [q] to quit: (default: go) 5.
  • Page 21: Rebooting The System

    Rebooting the System 6. Press to select all. ENTER The system installs the software and displays several status messages. When the software installation is complete, the system displays the message: Installation of Enhanced List Application Package was successful. Insert a tape into the Tape Drive. Type [go] when ready or [q] to quit: (default: go) 7.
  • Page 22 Installation 3. Press (F3) SAVE The system stops the voice system and displays the a series of status messages. When the voice system has stopped, the system displays the message: The Voice System has stopped. Press Enter to Continue. 4. Press ENTER 5.
  • Page 23: Administering Audix For Ela

    Administering AUDIX for ELA Overview To define the ELA server and functionality to AUDIX: Contact Professional Services (or your account representative, if you did not contract with Professional Services) to have ELA installed. Contact Professional Services (or your account representative, if you did not contract with Professional Services) to have ELA activated.
  • Page 24: Activating Ela

    Administering AUDIX for ELA Activating ELA After the ELA installation is complete, contact your Professional Services (or your account representative, if you did not contract with Professional Services). The technician from the remote support center will access your system remotely and activate the ELA feature.
  • Page 25: Increasing The Number Of Mailing Lists Allowed On The System

    Increasing the Number of Mailing Lists Allowed on the System 3. Ensure the following fields are set to ON: Enhanced List Application TCP/IP Administration 4. If either of these fields is OFF, and you purchased/installed ELA, call the support center to request that the features be enabled for your Lucent platform.
  • Page 26: Defining An Ela Class Of Service

    Administering AUDIX for ELA 6. Press (F3) to save the information in the system database. ENTER The cursor returns to the command line, and the system displays the message Command Successfully Completed. 7. Continue with the next procedure or enter exit to leave AUDIX Administration.
  • Page 27 Defining an ELA Class of Service Figure 3-2. Class of Service Screen, Page 1; Defining a Class of Service for ELA 3. Although not required, we recommend that you change the name of the COS to be more descriptive, for example, enter ELA in the Name: field. NOTE: You should write down the COS number.
  • Page 28 Administering AUDIX for ELA Figure 3-3. Subscriber Class of Service Parameters Screen, Page 2; Enabling ELA on a COS Basis 7. Enter the following information: 14 in the Retention Times (days), New: field. (This setting acts as a safety measure, should ELA encounter an operational problem, and cannot send messages for a couple of days.) 14 in the Retention Times (days), Old: field.
  • Page 29: Setting Up Ela And Shadow Mailbox Community Ids

    Setting Up ELA and Shadow Mailbox Community IDs 8. Press (F3) to save the information in the system database. ENTER The cursor returns to the command line, and the system displays the message Command Successfully Completed. 9. Continue with the next procedure or enter exit to leave AUDIX Administration.
  • Page 30: Before You Begin

    Administering AUDIX for ELA Let’s say you set up the enhanced-list mailbox community to be Community 10. Community 10 is given permission to send to all other communities (except the shadow mailbox community). Then, you set up a special user community, Community 9, and administer Community 9 to send to all communities (except the shadow mailbox community).
  • Page 31 Setting Up ELA and Shadow Mailbox Community IDs 2. At the enter command: prompt, enter either: Full Command Version Short Command Version change system-parameters sending-restrictions ch sy s The system displays the Sending Restrictions screen (Figure 3-5). Example administration for: Users w/ access to ELA in Comm ID = 9* Enhanced List Mailbox Comm ID = 10 Shadow Mailbox Comm ID = 11...
  • Page 32: Shadow Mailbox Community Id

    Administering AUDIX for ELA access to enhanced lists from sending a message to an Enhanced List. Following the example discussed under "Things to Consider" on page 3-19, there would be an r in the field corresponding to the intersection between Sender Community 1 (the default user community) and Recipient Community 10 (the Enhanced List Mailbox Community).
  • Page 33: Administering Tcp/Ip

    Administering TCP/IP Administering TCP/IP If your system is already connected to the LAN, you can skip this procedure. However, you need to know the IP Address to administer the trusted server, so — even if your system is already networked — perform step 1 of this procedure and write down your system’s IP address.
  • Page 34 Administering AUDIX for ELA Figure 3-6. TCP/IP Administration Window; Administering TCP/IP for Enhanced-List Application (ELA) 2. Enter the AUDIX server name in the UNIX Machine Name: field. This name should be listed on the Installation Information worksheet, or you can obtain this name from your PC/LAN administrator. This is a case-sensitive field, so capital letters must be typed as capitals, and lowercase letters as lowercase.
  • Page 35 Administering TCP/IP 5. Enter the default gateway IP address in the Default Gateway IP Address: field. The default gateway IP address is the address of the gateway router that serves to connect to addresses on other LANs. This field is left blank if the Lucent I system will only be communicating with other machines on NTUITY...
  • Page 36: Setting Up Imapi Sessions For Trusted Server Access

    Administering AUDIX for ELA NOTE: The changes to your system will not take effect until you reboot your system. See your I Messaging Solutions Release 4 Administration NTUITY book for instructions. Setting Up IMAPI Sessions for Trusted Server Access Whenever a trusted server accesses an AUDIX mailbox, it uses an IMAPI session.
  • Page 37 Setting Up IMAPI Sessions for Trusted Server Access Figure 3-8. System-Parameters IMAPI-Options Screen, Page 1; Setting IMAPI Sessions for Trusted Server Access NOTE: The following contain instructions for the fields that directly relate to ELA. See your I Messaging Solutions Release 4 Administration book. for NTUITY complete field descriptions and to understand their implications.
  • Page 38: Defining Two Ela Trusted Servers

    Administering AUDIX for ELA 8. Press (F3) to save this information to the system database. ENTER The cursor returns to the command line, and the system displays the message Command Successfully Completed. 9. Continue with the next procedure or enter exit to leave AUDIX Administration.
  • Page 39 Defining Two ELA Trusted Servers The TCP/IP address for the AUDIX server (see page 3-23). You will perform this procedure twice, first for the ELA administrative server, and then for the ELA delivery server. To add the ELA trusted servers to the I NTUITY AUDIX server: 1.
  • Page 40 Administering AUDIX for ELA , enter name for the first ELA trusted In the Trusted-Server Name: field server. (See the Note below for tips on trusted server names.) This name must be a unique 1- to 10-printable character entry. Additionally, this name cannot start with a number and cannot contain any embedded spaces, for example, denver 1 is not allowed, but denver_1 is allowed.
  • Page 41 Defining Two ELA Trusted Servers 11. Do you want to administer an IMAPI password? If yes, follow the procedures for setting the IMAPI password in your Messaging Solutions Release 4 Administration book before NTUITY proceeding to the next section. If no, go to Chapter 4 to Administer ELA, or enter exit to leave AUDIX Administration.
  • Page 42 Administering AUDIX for ELA Issue 1 July 1997...
  • Page 43: Administering Ela For Audix

    Administering ELA for AUDIX Overview Now that the AUDIX system knows about the ELA trusted servers, you can do the initial administration of the ELA system. To make ELA fully functional, you must: Define the AUDIX server to ELA and administer access Create enhanced lists Add members to enhanced lists Record a name for the enhanced lists (optional)
  • Page 44 Administering ELA for AUDIX Enhanced-list mailbox and shadow mailbox Community IDs (see page 3-20) ELA Class of Service (see page 3-16) To administer the ELA server: 1. Starting from the main menu (Figure 3-1 on page 3-14), select: > Enhanced-List Manager >...
  • Page 45 Defining the AUDIX server and Administering Access Table 4-1. Field Definitions: Set Up Enhanced-List System Data Window Field Name Description/Procedure System Login: Enter sa (system administrator login) or vm (voice mail administrator login). Valid Input: sa, vm NOTE: Administrators using the vm login cannot administer enhanced lists or ELA trusted servers.
  • Page 46 Administering ELA for AUDIX Table 4-1. Field Definitions: Set Up Enhanced-List System Data Window — Continued Field Name Description/Procedure Password: Enter the Administrative trusted server password (see page 3-30). Valid Input: 5- to 10-alphanumeric characters Delivery Trusted-Server Name: Enter the name of the delivery trusted server that you administered in AUDIX.
  • Page 47: Guidelines For Naming Enhanced Lists

    Guidelines for Naming Enhanced Lists Table 4-1. Field Definitions: Set Up Enhanced-List System Data Window — Continued Field Name Description/Procedure DEFAULT ENHANCED-LIST Enter the number of the COS assigned to the enhanced-list MAILBOX ATTRIBUTES mailbox and the shadow mailbox. Class of Service: ELA uses this COS number when you create new enhanced lists.
  • Page 48: Creating Enhanced Lists

    Administering ELA for AUDIX Give enhanced lists names that reflect an organization or a function. Include the word list . Examples: — Marketing_Dept_List — Maxfield_List — Western_District_Salesforce_List If you want all enhanced lists to be grouped together, put the word list first. Examples: —...
  • Page 49 Creating Enhanced Lists Figure 4-2. Administer Enhanced-Lists Window 2. Press (F4) NEW E-LIST The system displays the New Enhanced-List window (Figure 4-3). Figure 4-3. New Enhanced-List Window 3. Complete the fields in this window using the information in Table 4-2. Issue 1 July 1997...
  • Page 50 Administering ELA for AUDIX Table 4-2. Field Definitions: New Enhanced List Window Field Name Description/Procedure List Name: Enter a name for the list. Use the "Guidelines for Naming Enhanced Lists" on page 4-37. Valid Input: 1- to 29-alphanumeric characters Extension: Enter the local extension for the list mailbox.
  • Page 51: Guidelines For Selecting Enhanced-List Members

    Creating Enhanced Lists Guidelines for Selecting Enhanced-List Members The following subscribers can be members of an enhanced list: Local and remote subscribers. These members can be other enhanced lists. Call delivery numbers, including fax machines E-mail subscribers who are serviced by other trusted servers, including Lotus Integrated Messaging AMIS pre-administered subscribers The following cannot be members of an enhanced list:...
  • Page 52 Administering ELA for AUDIX Figure 4-4. Enhanced List Membership for Listname Window 2. Press (F4) ADD MEMBER The system displays the Add Member data entry window (Figure 4-5). Figure 4-5. Add Member Window; Adding Members to an Enhanced List 3. Enter one of the following: The user’s name as it appears in the AUDIX system.
  • Page 53: Adding/Deleting Members To An Enhanced List

    Creating Enhanced Lists 4. Press (F3) to save this information in the system database. SAVE NOTE: The Entries: field at the top of the Administer Enhanced-Lists window increments each time you add a new member to the list. 5. Repeat Step 3 and Step 4 to continue adding member names, extensions, and e-mail addresses.
  • Page 54 Administering ELA for AUDIX The system displays the Administer Enhanced-Lists window (Figure 4-2). The names of your enhanced lists display in the window (along with other descriptive data). 2. Using the arrow keys, select the list you would like to add members to. If the list is not on the visible page, select the list by one of the following means: Press...
  • Page 55 Creating Enhanced Lists Delete a member from the list (Step 6) Print the list to your system printer (Step 7) Adding a Member 4. Press (F4) ADD MEMBER The system displays the Add Member data entry window (Figure 4-5 on page 4-42).
  • Page 56: Deleting An Enhanced List

    Administering ELA for AUDIX Deleting a Member 6. To delete a member: a. Locate the member name to be deleted. See ‘‘Finding a Member’’ above. b. Press (F7) DELETE MEMBER The system displays the confirmation message: CONFIRM: Deleting Name= List - Listname Extension/Address= Listextension Enter y to continue, n to abort.
  • Page 57 Deleting an Enhanced List 2. Use the arrow keys to highlight the line that represents the list you want to delete. If the list to be deleted does not appear on the visible page, select the list by one of the following means. Press until the desired list displays.
  • Page 58: Recording Names For Enhanced Lists

    Administering ELA for AUDIX Recording Names for Enhanced Lists Once you have established an enhanced list, is a good idea to record a name for the list. That way, users will hear a meaningful name for the list when they send a message to an enhance- list mailbox for distribution.
  • Page 59 Testing I Enhanced Lists NTUITY "Defining an ELA Class of Service" on page 3-16 "Setting Up ELA and Shadow Mailbox Community IDs" on page 3-19 "Administering TCP/IP" on page 3-23 "Setting Up IMAPI Sessions for Trusted Server Access" on page 3-26 "Defining Two ELA Trusted Servers"...
  • Page 60 Administering ELA for AUDIX Issue 1 July 1997...
  • Page 61: Preventative Maintenance And Troubleshooting

    Preventative Maintenance and Troubleshooting Overview This section describes how to check for system alarms relating to ELA and how to diagnose common application and end-user problems. Checking the Administrator’s Log The system warns you of potential administrative problems with ELA by displaying a minor and warning message (Alarms: w or Alarms: m) on the AUDIX Administration status line when it logs an administration event.
  • Page 62: Checking The Delivery Failure Log

    Preventative Maintenance and Troubleshooting 5. Press (F3) to display the alarm entries. SAVE 6. Examine the displayed entries. See the Lucent I ™ Messaging NTUITY Solutions Release 4 Alarm and Log Messages, 585-310-566 for a list of events and alarms, and associated repair procedures. 7.
  • Page 63 Checking the Delivery Failure Log Table 5-1. Field Definitions: Enhanced-List Delivery Failure Log Window Field Name Description/Procedure Date The calendar date the delivery failure occurred Time The time that delivery failure occurred Message Originator The address of the user who sent the message to the enhanced list for distribution The address is in the format address@machine where address can be the telephone extension or the network (e-mail) address.
  • Page 64: Delivery Failure Codes

    Preventative Maintenance and Troubleshooting Delivery Failure Codes Delivery failure logs contain the following codes: Table 5-2. Delivery Failure Codes Reason of Failure Description Full mailbox The recipient has a full mailbox. Could not locate ELA could not locate the recipient. Transmission probs Transmission difficulties occurred.
  • Page 65: Troubleshooting Ela

    Troubleshooting ELA Troubleshooting ELA Table 5-3 lists questions users ask the system administrator and suggested remedies to commonly encountered system problems. Table 5-3. User Questions or System Functionality Symptoms Question/Symptom Possible Cause Answer/Suggested Remedy During an upgrade failure, Use the li cos command from AUDIX installer/administrator Administration to determine the ELA cannot differentiate...
  • Page 66 Preventative Maintenance and Troubleshooting Table 5-3. User Questions or System Functionality Symptoms — Continued Question/Symptom Possible Cause Answer/Suggested Remedy Recipient claims s/he did Mailing list not Check the mailing list for the recipient’s not get an ELA message. current name. Administer, if necessary. Subscriber’s Check the Subscriber screen for the mailbox not...
  • Page 67 Troubleshooting ELA Table 5-3. User Questions or System Functionality Symptoms — Continued Question/Symptom Possible Cause Answer/Suggested Remedy “Everyone else seemed to User mailbox full Check the List Measurements Subscriber have received their Day screen for the affected user. Look at enhanced-list message.
  • Page 68 Preventative Maintenance and Troubleshooting Issue 1 July 1997...
  • Page 69: Alarms

    Alarms Overview The following alarms are associated with the Enhanced-List Application. DELIVTS Resource Type Alarm Code: 1 Event ID: ELA-delivts01 Alarm Level: Warning Description: Trusted-server data lost, re-enter or restore. Repair Action: There are two recovery methods: Access the Set Up Enhanced-List System Data window and re-enter all field information.
  • Page 70 Alarms Alarm Code: 2 Event ID: ELA-delivts02 Alarm Level: Warning Description: Trusted-server data partially lost, re-enter or restore. Repair Action: There are two recovery methods: Access the Set Up Enhanced-List System Data window and re-enter all field information. Restore data from the most recent backup of system data. See Chapter 3, “Common System Procedures,”...
  • Page 71: Registry Resource Type

    REGISTRY Resource Type 2. Verify/administer the screen information, as required. 3. Repeat for the delivery trusted server. 4. Enter ch imapi and verify/administer as required. 5. When complete, enter the correct information in the Set Up Enhanced-List System Data window. REGISTRY Resource Type Alarm Code: 1 Event ID: ELA-registry01...
  • Page 72: Shadow Resource Type

    Alarms SHADOW Resource Type Alarm Code: 1 Event ID: ELA-shadow01 Alarm Level: Warning Description: Shadow mailbox data lost, re-enter or restore. Repair Action: There are two recovery methods: Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox extension and community ID. If a shadow mailbox exists at the extension entered, the system displays a system prompt to that effect.
  • Page 73 SHADOW Resource Type Alarm Code: 3 Event ID: ELA-shadow03 Alarm Level: Warning Description: Shadow mailbox data corrupt, re-enter or restore. Repair Action: There are two recovery methods: Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox extension and community ID. If a shadow mailbox exists at the extension entered, the system displays a system prompt to that effect.
  • Page 74 Alarms Repair Action: Access the Set Up Enhanced-List System Data window and re-enter the shadow mailbox extension and community ID. If a shadow mailbox exists at the extension entered, the system displays a system prompt to that effect. If a shadow mailbox does not exist at the extension entered, a new mailbox will be created.
  • Page 75: El - Enhanced-List Application

    EL — Enhanced-List Application If you regularly get this alarm, the following questions can help you evaluate how your business uses ELA: Do your subscribers use large enhanced lists too frequently? Are they being used for trivial or non-business purposes? Are subscriber mailboxes too small? Should you increase mailbox space or purchase more hours for storage? Is the ELA class-of-service correct? (Check the value in the Mailbox...
  • Page 76 Alarms Event ID: ELA-lostlock01 through ELA-lostlock10 Description: Messages to an enhanced list could not be delivered because someone was logged into the shadow mailbox. Repair Procedure: No one should ever be logged into the shadow mailbox. However. if someone is, change the password for the shadow mailbox as follows: 1.
  • Page 77 EL — Enhanced-List Application Repair Procedure: Evaluate list membership hierarchy and delete unnecessary nesting so that ELA can handle delivery of the message. See Lucent I Messaging Solutions NTUITY Release 4 Administration, 585-310-564 for procedures. Event ID: ELA-loopvioltn Description: There are two enhanced lists that refer to each other. For example, enhanced list 1 contains enhanced list 2 as a member, and enhanced list 2 contains enhanced list 1 as a member.
  • Page 78 Alarms 2. Verify that the shadow mailbox belongs to a community that cannot receive messages. NOTE: The sending restrictions must be identical on all machines in the AUDIX network. Check the sending restrictions on all NTUITY machines. See Lucent I Messaging Solutions Release 4 Administration, NTUITY 585-310-564 for more detailed procedures.
  • Page 79 Index activating administering COS alarms characteristics administering community IDs AUDIX delivery failure codes domains enhanced lists TCP/IP hardware requirements administrator’s log installation alarms LAN administration ELA-badreca01 through ELA-badreca12 logs ELA-chkrestrct mailboxes ELA-delivts01 mailing lists ELA-delivts02 passwords ELA-delivts03 planning for ELA-delivts04 ports ELA-delivts05 sending restrictions...
  • Page 80 Index trusted servers definition IMAPI sessions IP addresses names LAN administration security logs delivery failure virus detection virus prevention mailboxes mailing lists AUDIX messaging traffic passwords IMAPI list mailbox system ports rebooting the system security e-mail external access passwords trusted servers virus prevention service degradation, ports and shadow mailbox...

Table of Contents