48 E-Mail List Server

The E-Mail List Server processes messages sent to Oracle Email public distribution lists. Messages sent to mailing lists of type 'List Server List' are queued into the List Queue by the SMTP Inbound Server. These messages are then picked up by the List Server for further processing and delivery.

48.1 Messages

This category graphs various metrics concerning the receipt and delivery of e-mail messages sent to distribution lists.

48.1.1 Message Processing Rate

This metric indicates the efficiency of the list servers. However, the value depends on several factors such as the type of list to which the messages are being sent, the number of members in the distribution list, the size and type of incoming messages.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Evaluation and Collection Frequency
All Versions	Every 10 minutes

User Action

This metric must be interpreted in conjunction with the Length of List Queue metric of the Oracle Collaboration Suite Database (mailstore) target. If the List Queue is also empty or near empty, there is no problem. It means there are very few messages being sent to distribution lists. This is normal. If the List Queue is long but the Message Processing Rate is low then users will experience delays in receiving messages delivered to distribution lists. Check the following:

First, use the monitoring tools available on your operating system (for example, sar and top,) to check for sufficient operating system resources.
If operating system resources are available, message delivery may be slow. Check the list server logs files for any errors accessing the Oracle directory server access and/or the Oracle Collaboration Suite Database (mailstore).
Check the Messages metrics in the SMTP Inbound and Outbound Servers. These may also provide some information, because most of the delivery related problems are common to the SMTP and List Servers.

48.1.2 Number of Messages Being Processed

This metric indicates the number of messages that are currently being processed by the List Server.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Evaluation and Collection Frequency
All Versions	Every 10 minutes

48.2 Resource Usage

This category measures the resource usage by the list servers on a host. Resources usage of host resources such as CPU and Memory can be obtained from the Host target metrics.

48.2.1 Database Connections In Use

This metric measures the number of database connections to the Oracle directory server currently being used by the List Server. The List Server can be configured to pre-establish a pool of connections to the Oracle directory server, enabling the List Server to quickly access directory information when needed. The number of connections being used at a particular time depends on the number of messages being processed by the List Server at that time. Connections that are idle for long periods (as determined by the LDAP Connection Pool timeout value) will be closed automatically.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Evaluation and Collection Frequency
All Versions	Every 10 minutes

48.3 Response

This category contains metrics that provide information about the Up/Down status of the List Server.

48.3.1 Status

This metric provides information about the Up/Down status of the List Server and alerts you when the status is down. The List Server shows a status of Down when all List processes on the host are down.

Metric Summary

The following table shows how often the metric's value is collected and compared against the default thresholds. The Consecutive Number of Occurrences Preceding Notification column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Table 48-1 Metric Summary Table

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold'	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
All Versions	Every 5 Minutes	After Every Sample	=	Not Defined	0	1	E-Mail List Server not running

User Action

You can restart the List Server by selecting the target and clicking the Restart button on the Email Application home page in Enterprise Manager. To investigate why the List Server is down, check for any alerts that may have been generated. If the List Server does not restart, probable causes are an inability to connect to at least one of the mail information stores or the system's Oracle directory server. Check the server log file for more details. Use esd_logscan.pl to scan the server log files.