• Enable inbound connections, allowing the channel to accept new inbound connections.
This may be a no-op for some channels.
• Disable inbound connections, preventing the channel from accepting new inbound
connections. Existing inbound connections are unaffected. This may be a no-op for some
channels.
• Enable outbound connections. This may be a no-op for some channels.
• Disable outbound connections, preventing the channel from making new outbound
connections. Existing outbound connections are unaffected. This may be a no-op for
some channels.
• Disconnect all incoming connections. This may be a no-op for some channels.
• Clear delay. This clears any delay which may have been applied to the channel itself.
• Set 1 minute delay. Applies a one minute delay to the channel.
• Set 10 minute delay. Applies a ten minute delay to the channel.
• Set 1 hour delay. Applies a one hour delay to the channel.
• Downwards force attempt. This clears any delay on the channel, enables the channel,
and then performs a "downwards force attempt" on any subordinate Peer MTA or
messages.
• Connect to Peer MTA. This allows an arbitrary Peer MTA name to be entered and passed
to the channel as the argument of a "connect" instruction. The name entered should be
in the appropriate format for the channel protocol: e.g. a mail domain name for an SMTP
channel or the Distinguished Name of a Peer MTA's x400p1 channel for a x400p1
channel. This is a no-op for non-protocol channels.
• Limit by priority. This allows you to configure the channel to only process Urgent or
Urgent and Normal priority messages, with an optional time range, Lower-priority
messages will be ignored, even if there are no messages of the selected higher priority
to process. The priority limitation can be cleared by chosing the "All messages" option.
• Timeout all messages. This allows all messages queued on the channel to be timed out.
The messages will be queued onto the Housekeeper channel for processing, and
non-delivery reports will be generated for any message recipients for which they were
requested.
• Delete all messages. This allows all messages queued on the channel to be deleted. No
non-delivery reports will be generated.
• Reprocess queue. This causes the Queue Manager to perform a routing calculation for
each recipient of every message currently queued on this channel. If routing or other
configuration changes have been made since messages were queued, this may cause
messages to be requeued on different channels or for transfer to different Peer MTAs.
5.2.3
Peer MTA
The following operations can be performed on individual Peer MTAs:
• Alter Peer-MTA Agreement. This opens (or switches to) the Switch Configuration
Management view, and selects the configuration entry for the Peer-MTA agreement for
this Peer MTA, if one exists.
• Enable the Peer MTA.
• Disable the Peer MTA. This prevents the channel from processing any messages which
are queued on this Peer MTA.
• Enable inbound connections, allowing the channel to accept new inbound connections
from this Peer MTA. This may be a no-op for some channels.
• Disable inbound connections, preventing the channel from accepting new inbound
connections from this Peer MTA. Existing inbound connections are unaffected. This
may be a no-op for some channels.
• Enable outbound connections. This may be a no-op for some channels.
Switch Operations
11
M-Switch Operator's Guide
