The Suspend-Message cmdlet prevents delivery of one or more messages that are in a queue on the Hub Transport server or the Edge Transport server. A message that is already in delivery will not be suspended. Delivery will continue and the message status will be PendingSuspend. If the delivery fails, the message will re-enter the queue and it will then be suspended. You cannot suspend a message that is in the Submission queue or in the poison message queue.
A message that is being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message will be suspended in a single queue if that identity matches only a single message. If the identity matches more than one message, you will receive an error. To suspend a message in more than one queue in a single operation, you must use a filter. You must use an Identity parameter or a Filter parameter. These two parameter sets are mutually exclusive.
You can suspend a message on a remote server by including the server name as part of the Identity parameter or by using the Server parameter with the Filter parameter. If you do not specify a server, the command runs against only the local server.
To run the Suspend-Message cmdlet, the account you use must be delegated the Exchange Server Administrator role and local Administrators group for the target server.
To run the Suspend-Message cmdlet on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.