The Exchange Edge default Receive connector gets unexpectedly disabled even though the Email policy is not configured


You have installed Forefront TMG 2010, Exchange 2010 Edge role and Forefront Protection for Exchange (FPE) 2010 on the same machine. You do not want to use the Email policy configuration integration feature of Forefront TMG (in this case TMG won’t manage the Exchange Edge and FPE settings), in other words you have not executed the “Configure Email Policy” wizard in the TMG Management console. In this situation the E-Mail Policy settings appears like the figure below:


On Exchange Edge console you notice that the default Receive Connector of Exchange Edge gets disabled:



Forefront TMG is responsible for this behavior and the reason is that the property IntegrationEnabled of the SmtpProtectionConfiguration COM object is wrongly set to TRUE by default during TMG setup. See

Note: This behavior should be fixed in a future update of TMG.

Current Resolution

The recommendation is to use the integration mode so that TMG manages Exchange Edge and FPE settings automatically for you (at least the settings exposed in the TMG management console). If you choose to use the integration mode you won’t run into this issue as TMG will automatically manage the SMTP connectors defined in Exchange Edge.

However if you don’t want to use this integration mode for some reasons, the current workaround to this problem is to set the Email Policy Integration mode to Disabled (as indicated in the screenshot below) and apply the change. This will set the COM property IntegrationEnabled to False.


Eric Detoc
Escalation Engineer
Microsoft CSS Forefront Security Edge Team

Technical Reviewer
Yuri Diogenes
Senior Support Escalation Engineer
Microsoft CSS Forefront Security Edge Team

Comments (2)

  1. The problem with enabling the integration mode is, that TMG overwrites *everything* on the receive connector – although it is mentioned that it doesn't/shouldn't on Technet. What I'm referring to is for example logging settings. These get overwritten as soon as you enable integration mode. Even when I enable logging afterwards again, it get's overwritten after a few minutes. I'm waiting for a solution for this since TMG RTM! Several posts in Technet Forums show that many people face this issuse. Hopefully there will be a fix for both issues – the one that you descrive in this blog post as well as for the issue that I described here… Christian Schindler

  2. Eric Detoc says:

    Thanks Christian pour your comment. Update1 includes some fix for the "overwriting"  behavior that you mention. have you recently try the Update1?

Skip to main content