6.10 Creating an SMTP Connector | Monitoring and Managing Microsoft Exchange 2000 Server (HP Technologies)

Chapter 6 - Managing E-Mail Connectivity
Monitoring and Managing Microsoft Exchange 2000 Server
by Mike Daugherty
Digital Press 2001

6.12 Managing queues and messages in queues

Any messaging environment consists of a set of cooperating processes running on various systems. Messages passed from one process to another are often queued until the receiving process can handle the new message.

Sometimes the sending and receiving process are on the same system, and sometimes they are on separate systems. For example, within the Exchange SMTP virtual server, messages can be queued waiting for the virtual server to perform directory lookup or waiting for the routing engine to determine the appropriate next -hop for the message. SMTP connectors, X.400 connectors, Novell GroupWise connectors, Lotus Notes connectors, and all other connectors will queue messages waiting to establish network connections with messaging processes running on other systems.

The Exchange System Manager program includes a facility that allows you to easily manage these messaging queues and the messages contained within those queues. This can be used for SMTP virtual servers and Microsoft Exchange connectors such as the X.400 Connector, Lotus Notes Connector, Lotus cc:Mail Connector, and Novell GroupWise Connector.

Using the Performance Monitor to track the number of entries in queues is one of the best ways to detect potential messaging transport problems. If the Performance Monitor identifies a queue containing a large number of entries, you can use the Exchange System Manager to view the messages waiting to be transferred. A large number of messages may be queued for a variety of reasons. For example, an extremely large message may be at the head of the queue and its delivery is simply taking a long time, or the message at the head of the queue may have a problem that will prevent it from ever being delivered, or you may simply have a temporary increase in the number of messages being sentpossibly caused by an automated process. Until you examine the entries in the queue, you will not know if the length of the queue is due to a problem or just temporarily heavy usage. If a message is causing a problem, you may choose to remove the message from the queue and return it to the sender with a non-delivery report (NDR).

The Exchange System Manager program provides administrators with the functionality needed to examine and manage Exchange queues and the messages contained in those queues. You should not wait for a problem before you examine the messaging queues. You should schedule regular time to examine the queues since a backed -up messaging queue can be an early indicator of more serious system or networking problems. You should periodically examine the queue and message states to determine if messages are flowing properly. When the queue or message states indicate a possible problem, the queue information may help you identify the source of the problem.

6.12.1 Viewing queue summaries

Your Exchange system includes a variety of messaging queues. The exact number and type of queues depends upon the protocols supported in your environment. Using Exchange System Manager, you can manage messaging queues for Simple Mail Transfer Protocol (SMTP), X.400, and foreign e-mail connectors such as those for GroupWise, Lotus Notes, and cc:Mail.

Two types of queues are used within Exchange:

System queues . Before a message can be sent from one system to another, several processes examine and prepare the message for its journey over the network. These system processes include activities such as message categorization, address resolution, content conversion, and next-hop routing calculation. System queues hold messages awaiting this type of processing. System queues are always visible using Exchange System Manager. If messages remain in your system queues for long periods, it can be an indication of problems with the systems messaging processes.
Link queues . Sending a message from one system to another often requires that the message be relayed through one or more intermediate servers in its journey to its final destination. The next server in the journey is known as the next-hop server. Once the routing engine has determined the next-hop server for a message, the message is added to a link queue for the next-hop server. All messages destined for the same next-hop server are queued to the same link queue. Messages remain in a link queue until Exchange can establish an active connection with, and can transfer the message to the next-hop server. Link queues are named for the next-hop server. For example, SMTP messages queued for delivery to recipients on compaq.com will be added to a link queue named compaq.com (Remote delivery) . These next-hop link queues are created and removed as needed. For example, if the next-hop for a message is the compaq.com domain, the virtual server will create a temporary link queue for the compaq.com domain. Once all messages in the link queue have been transferred to compaq.com, the virtual server removes the queue. If the messages cannot be transferred to the next-hop (e.g., compaq.com), they are re-queued for later retry .

The types of system queues available to you through Exchange System Manager depend upon the protocols being used. To access the SMTP virtual server queues using Exchange System Manager, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues. SMTP virtual servers have the following types of system queues:

Local domain name (Local Delivery) . This queue contains messages that are queued for delivery to a mailbox on the local Exchange server. The queue is named for the local e-mail domain. For example, the queue for the compaq.com domain would be compaq.com (Local delivery) .
Messages awaiting directory lookup . Messages are retained in this queue until Exchange can expand any distribution lists and/or lookup the message recipients in the Active Directory.
Messages waiting to be routed . This queue contains messages while the next-hop server is determined. Once the next-hop server is determined, the message is moved to the link queue for the next-hop server.
Final destination currently unreachable . If Exchange cannot find an active network pathway to the final destination server, it adds the message to this queue.
Pre-submission . This queue contains new messages that have been accepted by the SMTP virtual server, but for which the processing has not begun.

To access X.400 queues using Exchange System Manager, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues. The X.400 service uses only one queue:

PendingRerouteQ . This queue is always visible in System Manager, but it will be empty unless there are messages pending reroute after a temporary connection problem.

You can access connector queues such as GroupWise and cc:Mail by expanding Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues. These, and other MAPI-based foreign connectors, may have the following types of system queues:

Note	Not all of these system queues will appear for all foreign e-mail connectors.

READY-IN . This queue contains messages that have arrived from the foreign e-mail system (e.g., cc:Mail). The connector has converted the message format (e.g., content conversion, attribute mapping, etc.), but the recipient addresses have not yet been resolved.
MTS-IN . This queue contains messages that have arrived from the foreign e-mail system (e.g., cc:Mail). The connector has looked up the recipient addresses in the Active Directory and the messages are ready for delivery.
MTS-OUT . This queue contains messages being sent from Exchange to the foreign e-mail system. These messages are awaiting address resolution.
READY-OUT . This queue contains messages being sent from Exchange to the foreign e-mail system. The addresses have been resolved but the connector has not yet converted the message format.
BADMAIL . When the connector encounters a message that cannot be successfully processed , it adds this to this queue. The connector will not retry these messages, and they will remain in the BADMAIL queue until the administrator deletes them.

You can use the following procedure to display summary information about the messaging queues:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
Figure 6.26: SMTP virtual server queues
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select Queues to display a summary of the queues for this SMTP virtual server, X.400 object, or connector. (See Figure 6.26.)

Table 6.1 lists the information that is displayed in the details pane. The System Manager displays the columns in the order listed in this table. You can modify the order of the columns, hide columns, or add columns by selecting Choose Columns from the View menu.

6.12.2 Viewing messages in a queue

When the Performance Monitor indicates that a messaging queue may not be working, examining the messages in the queue can often provide clues to help identify the problem. Viewing individual messages gives you more granularity for performing management tasks such as freezing or deleting messages.

Table 6.1: Queue Summary Information
Property	Description
Name	This is the name of the message queue.
Connection State	The connection state will provide a quick indication that a queue is experiencing problems. There are several possible states: Disabled . The link between this server and the next hop server is not available. Active . There is an active connection between this server and the next-hop server. Ready . The queue is ready to have a connection allocated to it. Retry . Previous connection attempts have failed and the server is waiting for another attempt. An administrator can use the Force Connection command to change a queue in the Retry state to Active. This causes the queue to continue processing messages as if the retry time had been reached. If the queue was in the Retry state due to a network or server error, the state will quickly return to the Retry state if the underlying error has not been corrected. Scheduled . The queue is waiting for the next scheduled connection attempt. An administrator can use the Force Connection command to change a queue in the Scheduled state to Active. This causes the queue to continue processing messages as if the scheduled time had been reached. Remote . The queue is waiting for a remote dequeue command ( TURN /ETRN). Frozen . The administrator has frozen the queue to keep messages from exiting the queue. Additional messages may still be added to the queue. Freezing an Active queue immediately terminates the transport sessions for that queue.
Time of Submission of Oldest Msg	This is the time that the oldest message in the queue was submitted by the client. This time stamp provides an indication of how long messages have been queued waiting for delivery to the destination server.
Total Number of Msgs	This is the number of messages in the queue. A large number of queued messages can be an indication of a connection problem.
Total Msg Size (KB)	This is the total size of all messages in the queue.
Time of Next Connection Retry	This is the time when the next retry attempt will be made. If the queue is not in a Retry or Scheduled state, then this field will be blank. An administrator can use the Force Connection command to change a queue in the Retry or Scheduled state to Active.

However, viewing the individual messages in a queue is a resource intensive task. Therefore, messages are not automatically displayed. Instead, you must specifically ask the System Manager to display, or enumerate, the messages. You can either enumerate the first 100 messages in a queue or use a custom filter to select a subset of the queued messages. Once you enumerated the messages in a queue, the System Manager will display selected message properties in the details pane of the System Manager window.

Enumerate 100 Messages

The easiest way to display queued messages is to use the Enumerate 100 Messages command to quickly enumerate and display the first 100 queued messages.

You can use the following procedure to display the first 100 messages in a queue:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the queue that you want to enumerate. If you have previously enumerated the messages in this queue, the details pane will contain a list of queued messages. However, if you have not previously enumerated messages, the System Manager will display Enumerate messages from the queue node in the details pane to remind you that you must enumerate the messages.
Right-click on the queue, and select Enumerate 100 Messages to display queued messages in the details pane of the System Manager window. If there are no queued messages, the System Manager will display There are no matching messages queued in the details pane. If there are messages in the queue, the System Manager will display selected properties of each message in the details pane. Once messages have been displayed, you can sort the messages by selecting the column heading. An up or down arrow will appear in the sort column heading to indicate whether the messages are sorted in ascending or descending order. You can also individually examine, freeze, or delete the messages that are displayed.

Table 6.2 lists the message properties that are displayed in the details pane. The System Manager displays the columns in the order listed in this table. You can modify the order of the columns, hide columns, or add columns by selecting Choose Columns from the View menu.
You can double-click any message in the details pane to display the Properties dialog box for the queued message (Figure 6.27). The Properties dialog box includes additional information about the message. One of the key pieces of information is the Message ID, which can be useful for troubleshooting problems.

Using a custom filter to enumerate queued messages

Enumerating the first 100 messages is easy, but may not provide access to the messages you want. You can use the Custom Filter command to identify the types of messages you want to view. For example, you can use a Custom Filter to enumerate the largest messages, the oldest messages, frozen messages, messages larger than a specified size, messages older than a specified age, messages from a specific sender, messages being sent to a specific recipient, or all messages that have experienced a delivery failure. You can also specify combinations of these criteria.

You can use the following procedure to enumerate messages using a custom filter:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.

Table 6.2: Queued Message Properties
Property	Description
Sent From	This field identifies the sender of the message.
Priority	This is the message priority. The priority is protocol dependent and does not necessarily match the priority that the sender may have assigned to the message.
Message Subject	Because subject lines often contain confidential information, some companies may want to limit the number of people who can view the text in the subject line. For this reason, message subjects are not automatically displayed. To see subjects for messages in SMTP and connector queues, you have to first enable the feature by selecting Enable subject logging and display on the General tab of the servers properties.
# of Body Recipients	This is the total number of recipients for this message. The count includes CC and BCC recipients and all recipients included in distribution lists. If this value exceeds the destination servers limit for the number of recipients per message, then the message may be marked as undeliverable.
Message Size (bytes)	This is the total message size. If this value exceeds the destination servers message size limit, then the message may be marked as undeliverable.
Time of Submission	This is the time that the client submitted the message for delivery. For messages originating on your local server, this time stamp provides an indication of how long the message has been queued waiting for delivery to the destination server.
Time Received by Server	This is the time that the message was received by the Exchange 2000 server. If incoming messages remain queued for lengthy periods, it may be an indication that you have a problem with your Exchange environment.
Time Expires	This is the time that the Exchange system will discontinue attempts to deliver the message and will remove the message from the queue.
State	Queued messages have one of three states. Queued . The message is queued awaiting its first delivery attempt. Retry . Previous delivery attempts have failed and the message is queued for another delivery attempt. Frozen . The administrator has frozen the message to keep it from exiting the queue. This does not mean the message queue is frozen.

Figure 6.27: The Properties dialog box for a queued message

Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the desired queue.
Right-click on the queue, and select Custom Filter to display the Custom Filter dialog box.
Using the Action drop-down list, select Enumerate (Figure 6.28).
There are three ways to specify your selection criteria. The selection criterion varies by protocol, so SMTP, X.400, and the MAPI based connector queues may not support all of the following criteria.

Figure 6.28: The Custom Filter dialog box
- Use the following steps to enumerate the first, largest, or oldest messages in the queue:
  
  Select Select only the .
  
  Select First , Largest , or Oldest .
  
  Use the Number of messages field to specify the maximum number of messages to view.
- Use the following steps to enumerate all messages with specific characteristics:
  
  Select Select messages that are .
  
  Select the Frozen check box to select frozen messages.
  
  Enter a value into the Larger than field to select messages larger than the specified size.
  
  Enter values into the Older than fields to select messages older than the specified age.
  
  Enter sender IDs into the From field to select messages sent by certain users.
  
  Enter recipient IDs into the To field to select messages being sent to certain users.
  
  Select the Delivery failure check box to select messages that have experienced a delivery failure.
- To enumerate all messages in a queue, select Select all messages .
If you have a set of selection criteria that you use frequently, you can select the Set as default filter check box to save your selections.

Re-enumerate messages

You establish the criteria for enumerating messages using either the Enumerate 100 Messages command or by using a Custom Filter. Once the criteria are established, you can use the Re-Enumerate command to refresh the displayed messages based on the most current data. For example, over time messages will be removed from the queue as they reach their destination. Thus, the first 100 queued messages that are displayed in the details pane become invalid over time. The Re-Enumerate command can be used to find the current 100 queued messages. Similarly, if you have used a custom filter to enumerate all messages larger than 1MB, the Re-Enumerate command can be used to find newly queued messages that meet the criteria.

You can use the following procedure to re-enumerate messages:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the queue that you want to enumerate.
Right-click on the queue, and select Re-Enumerate. The Re-Enumerate option is only available if you have previously enumerated the messages in the queue.

6.12.3 Freezing and unfreezing a queue

Exchange messaging queues are very dynamic with messages constantly entering the queue, being processed, and then exiting the queue. For many troubleshooting activities, it is important to temporarily prevent messages from exiting a queue. This is known as freezing a queue. You can also freeze individual messages within a queue to prevent the selected messages from exiting the queue while allowing other messages to be processed.

When you freeze a queue, the connection state for the queue is changed to Frozen and the messages currently in the queue will not exit the queue (i.e., none of the currently queued messages will be delivered). Freezing a queue does not prevent new messages from being added to the queue. However, neither the current messages nor the newly added messages will be delivered until the queue is unfrozen.

You can use the following procedure to freeze or unfreeze an entire queue:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Note
X.400 queues cannot be frozen.
Select the queue you want to freeze or unfreeze.
Right-click on the queue, and select Freeze or Unfreeze. Freeze will change the connection state for the queue to Frozen and will prevent messages from exiting the queue. Messages will remain in the queue until the queue is unfrozen using the Unfreeze command.

6.12.4 Freezing and unfreezing selected messages in a queue

Just as you can freeze an entire queue to keep all messages from exiting the queue, you can select specific messages to freeze. Frozen messages will remain in the queue until they are unfrozen. Freezing a message is the best way to keep a suspicious message in the queue long enough for you to examine it. Freezing a message is also useful if a large message is blocking the queue. You can temporarily freeze the large message to allow other messages in the queue to be processed.

You can use the following procedure to freeze or unfreeze individual messages in a queue:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the queue containing the messages to freeze or unfreeze.
Right-click on the queue, and select Freeze to freeze the entire message queue. The Exchange message queues are dynamic with messages constantly entering and exiting the queues. It is important that you first freeze the queue before freezing individual messages in the queue. If you fail to freeze the queue, the messages that you select to freeze may continue to be processed and may exit the queue before they are actually frozen.
There are two ways to select the messages you want to freeze or unfreeze:
- Selecting individual messages from the details pane.
  - Enumerate or re-enumerate the messages in the queue.
  - In the details pane, right-click on the appropriate messages, and select Freeze or Unfreeze. Freeze will prevent messages from exiting the queues. The frozen messages will remain in the queue until they are unfrozen by the Unfreeze command. Freezing or unfreezing selected messages has no affect on other messages in the queue.
- Using a custom filter.
  - Right-click on the queue, and select Custom Filter.
  - In the Custom Filter dialog box, select Freeze or Unfreeze from the Action drop-down list.
  - Specify your selection criteria. You can freeze or unfreeze the largest messages, the oldest messages, frozen messages, messages larger than a specified size, messages older than a specified age, messages from a specific sender, messages being sent to a specific recipient, or all messages that have experienced a delivery failure. You can also specify combinations of these criteria.
Right-click on the queue, and select Unfreeze. This will unfreeze the queue without unfreezing the selected messages.

6.12.5 Deleting selected messages from a queue

Messages deleted from queues will not be delivered to their intended recipients. When you delete a message from a queue, it is goneforever. Because deletions are a permanent, destructive operation, you must take special care to ensure that you delete the intended messages. There are several ways you can delete messages from a queue. You can simultaneously delete all the messages in a queue with a single command. This is not advisable under most circumstances. It is much better to carefully select the individual messages you want to delete. This selection can be done by either selecting the messages from the details pane or by using a custom filter to delete messages that meet certain criteria. For example, you can use a custom filter to delete the five largest messages, or messages from a certain sender, or messages that have experienced delivery problems.

Even if you carefully select the messages to delete, you must ensure that you first freeze the message queue to ensure that the messages do not exit the queue during the selection process. The message queues are dynamic with messages constantly entering and exiting the queue. It is important that you freeze the queue during the deletion process to ensure that you delete the intended messages.

You can use the following procedure to delete individual messages from a queue:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the queue containing the messages to delete.
Right-click on the queue, and select Freeze to freeze the entire message queue. The Exchange message queues are dynamic with messages constantly entering and exiting the queues. It is important that you first freeze the queue before deleting individual messages from the queue. If you fail to freeze the queue, the messages that you select to delete may continue to be processed and may exit the queue before they are actually deleted.
There are two ways to select the messages you want to delete:
- Selecting individual messages from the details pane.
  - Enumerate or re-enumerate the messages in the queue.
  - In the details pane, right-click on the appropriate messages, and select Delete Messages (no NDR) or Delete Messages (send NDR). Delete Messages (no NDR) will delete the messages from the queue without notifying the sender. Delete Messages (send NDR) will delete the messages from the queue and will notify the senders of the messages using non-delivery reports (NDR).
- Using a custom filter.
  - First, freeze the messages you want to delete. Right-click on the queue, and select Custom Filter.
  - In the Custom Filter dialog box, select Freeze or Unfreeze from the Action drop-down list.
  - Specify your selection criteria. You can freeze or unfreeze the largest messages, the oldest messages, frozen messages, messages larger than a specified size, messages older than a specified age, messages from a specific sender, messages being sent to a specific recipient, or all messages that have experienced a delivery failure. You can also specify combinations of these criteria.
  - Next, display the messages that you have frozen. Right-click on the queue, and select Custom Filter.
  - In the Custom Filter dialog box, select Enumerate from the Action drop-down list.
  - Select the Frozen check box for the selection criteria. This will display the messages you want to delete. Review the message carefully to ensure that it includes only those messages that you want to delete. If it does not, then refine your custom filter selection criteria, or individually select messages from the details pane for deletion.
  - If the set of frozen messages matches the ones you want to delete, then proceed to delete the messages. In the Custom Filter dialog box, select Delete (no NDR) or Delete (Send NDR) from the Action drop-down list.
  - Select the Frozen check box for the selection criteria. This will delete all frozen messages from the queue.
Right-click on the queue, and select Unfreeze to unfreeze the queue.

6.12.6 Forcing a connection

Messages remain in queues until they can be delivered to the receiving process. In the case of sending a message from one system to another, the receiving process is on another system. Network or system problems can sometimes prevent immediate delivery of the message. In this case, the message is requeued and a retry is scheduled for a future time. If the problem has still not been corrected when the delivery attempt is retried, then the message is again re-queued. An administrator can use the Force Connection command to create an immediate connection to the remote server without waiting for the next retry time. You can use the following process to force an immediate connection.

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the queue for which you want to force a connection.
Right-click on the queue, and select Force Connection to force an immediate connection to a remote server without waiting for the next retry attempt.

6.12.7 Exporting queue and message contents

You may find it useful to export the contents of the details pane so you can import the data into another tool, such as Microsoft Excel, for analysis. You can use the following procedure to export all columns shown in the details pane into a comma-delimited or tab-delimited file:

Start the System Manager from the Windows 2000 Start menu by selecting Programs Microsoft Exchange System Manager.
Expand the appropriate sections to navigate to the Queues group:
- For SMTP queues, expand Administrative Groups administrative group name Servers server name Protocols SMTP SMTP virtual server name Queues.
- For X.400 queues, expand Administrative Groups administrative group name Servers server name Protocols X.400 Queues.
- For connector queues such as GroupWise and cc:Mail, expand Administrative Groups administrative group name Routing Groups routing group name Connectors connector name Queues.
Select the desired queue.
Right-click on the queue, and select Export List to display the Save As dialog box.
In the File Name field, enter a file name for the file you are creating. Use the Save as type drop-down list to select the desired file format. You can save the file as a comma-delimited file or a tabdelimited file. You can later import this file into a spreadsheet or database application for analysis.