Email Moderation is a new feature that allows a moderator to moderate emails before they reach their destination. If you have not read about moderation yet delight read the following the following post I wrote a few months ago:

http://clintboessen.blogspot.com/2009/06/exchange-2010-email-moderation.html

In this post we will be looking at how moderation works and the processes that go on in the back end.

The moderated transport attention consists of the following components:

Categorizer

The transport categorizer initiates the praise process. When the categorizer detects a moderated recipient while processing a message, it reroutes the message to the arbitration mailbox.

Store driver

The store driver processes the messages that the categorizer marks for moderation. When the store driver encounters such a message, it stores the original message in the arbitration mailbox and sends praise requests to the moderators. When a moderator responds with a choice, the store driver marks that choice on the message that’s stored in the arbitration mailbox. If an approved message is submitted again by the Information Assistant, the store driver removes the praise workflow wrappers so the message that’s delivered is identical to the original message submitted by the sender.

Information Assistant

The Information Assistant process monitors the arbitration mailbox. The Information Assistant resubmits any approved messages to the submission queue for delivery to the intended recipients, or it deletes rejected messages. The Information Assistant is also responsible for carriage rejection notifications to the sender. In addition, it cleans up the arbitration mailbox by deleting any stale or orphaned messages from the arbitration mailbox. For example, if a moderator austerely deletes an praise request instead of making a choice, the corresponding message waiting for praise in the arbitration mailbox needs to be removed by the Information Assistant.

Arbitration Mailbox

The arbitration mailbox is used to store the original message that’s awaiting praise. By defaulting, one arbitration mailbox is made for moderated transport during setup. It’s used for all moderated recipients. You can add additional arbitration mailboxes for load balancing purposes. If you’re by multiple arbitration mailboxes, you need to specify which mailbox to use for each moderated recipient.

What processes occur in the backend?

The following screenshot is taken from Microsoft’s TechNet Website:

1.The sender makes a message and sends it to the moderated recipient.

2.The categorizer intercepts the message, marks it for moderation, and then reroutes it to the arbitration mailbox.

3.The store driver stores the message in the arbitration mailbox and sends an praise request to the moderator.

4.The moderator uses the buttons in the praise request to any accept or reject the message.

5.The store driver marks the moderator’s choice on the original message stored in the arbitration mailbox.

6.The Information Assistant reads the praise status on the message stored in the arbitration mailbox, and then processes the message depending on the moderator’s choice:

6-a.If the moderator has approved the message, the Information Assistant resubmits the message to the submission queue, and the message is delivered to the recipient.

6-b.If the moderator has rejected the message, the Information Assistant deletes the message from the arbitration mailbox and notifies the sender that the message was rejected.

If the moderator doesn’t respond to the message within five days, the Information Assistant will delete the message from the arbitration mailbox and report the sender that their message has expired.

Handling Multiple Moderated Recipients

Taken from TechNet:

It’s possible to send a message to a assemble of recipients that includes both moderated recipients and recipients that aren’t moderated. In this case, a separate praise process occurs for each moderated recipient.

Consider a message that’s sent to 12 recipients, one of which is a moderated distribution assemble. The categorizer splits this message into two messages. One message is delivered immediately to the 11 recipients that aren’t moderated, and the second message is submitted to the praise process for the moderated distribution assemble.

If a message is intended for more than one moderated recipient, a separate copy is made for each moderated recipient and is submitted to the praise process.

A moderated distribution assemble may contain other moderated recipients. In this case, after the message to the distribution assemble is approved, a separate praise process occurs for each moderated recipient that’s a member of the distribution assemble. But, you can also enable the automatic praise of the distribution assemble members after the message to the moderated distribution assemble is approved. To do this, you set the BypassNestedModerationEnabled parameter of the moderated distribution assemble to $right by the Set-DistributionGroup cmdlet.

Moderation and Exchange 2007 Hub Transport Servers

If you have Exchange 2007 Hub Transport servers mixed with your Exchange 2010 environment you must configure an Expansion Server on any item you have moderated. If you do not do this, the store driver on the Exchange 2007 Hub Transport server will austerely deliver the message bypassing moderation. To enable an expansion server for a distribution assemble use the following command:

Set-DynamicDistributionGroup -Identity “GroupIdentity” -ExpansionServer “Exchange2010HubTransportServer”

So you want the basic cmdlet on how to enable moderation huh?

Not more than is an example on how you would go enabling moderation on a distribution assemble:

Set-DistributionGroup “All Employees” -ModerationEnabled $right -ModeratedBy “clint@kbomb.com.au”,”administrator@kbomb.com.au” -ByPassModerationFromSendersOrMembers “HR” -SendModerationNotifications Internal

Check it out:Clint Boessen’s Blog