Queue Viewer

Managing Connections

An active connection is needed to allow messages to be transported out of a link queue.

There are only two global actions that you can perform on all the queues in a given SMTP virtual server, X.400 object, or connector: Disable All Connections or Enable All Connections. These actions are performed at the main Queues node. Depending on the protocol (SMTP, X.400, or MAPI) these commands may not affect system queues.

In individual link queues, the following commands are used to manage connections:

Enable Connection
Disable Connection
Force Connection

See Manage Connections for information on how to execute these commands.

If a link between a queue and the next-destination server is not connected, its Connection State will be Disabled. If a link between a queue and the next-destination server is connected, the Connection State will be Enabled and can be any of the following: Active, Ready, Remote, Frozen, Retry, and Scheduled. These states are defined in the table below.

Force Connection allows administrators to create an Active link connection. If the server determines the connection to be remote, the state will be changed to Remote (however that change is made by the server).

Note Although Remote, Retry and Scheduled are valid connection states, the administrator will not be able to enforce them because they are determined by Exchange.

State	Icon	Definition
Active		Link queue has an active connection.
Ready		Link queue is ready to have a connection allocated to it.
Retry		A connection attempt has failed and the server is waiting for retry.
Scheduled		Waiting for a scheduled connection attempt.
Remote		Waiting for a remote dequeue command (TURN/ETRN).
Frozen		No messages will leave the link queue. Messages may still be inserted if the Exchange routing categorizer is still running.
Disabled		No messages will leave the link queue. This state is obtained when "DISABLEALL" is invoked on the Queues node.