If you are following my blog for a long time you probably read the post TMG E-Mail Protection Feature x Exchange 2010 SP1 (first published more than an year ago) when we were dealing with a major E-Mail protection issue on TMG. Due the nature of the integration between Forefront TMG and E-Mail Protection feature (Forefront for Exchange and Exchange Edge) I also wrote this presentation to assist you while troubleshooting this feature.
The good news is that Forefront TMG 2010 SP2 brings to you the following fixes that will alleviate lots of the issues that were present in the past with this integration:
Go get SP2 and enjoy it!!
I still have the problem that on a machine with Forefront TMG 2010 (SP1 update 1) / Forefront Protection for Exchange 2010 (11.0.713) and Exchange 2010 Edge Role (SP1 Rollup 4-v2) installed all additional receive connectors configured with EMC of Edge get overwritten by TMG Email Policy Integration.
Will that be fixed with TMG SP2?
AFAIK the recommendation to create all settings on Forefront TMG console rather than Exchange (and FPE) persists.
thanks for you reply, i've installed TMG SP2 now on my multi-homed Edge/TMG Server.
I still have the Problem that EMC configured Receiveconnectors get overwritten by TMG (Have found a workarround to disable edge-subscription, create smtp route, recreate edge-subscription) but there's still no way to configure RemoteIPRanges for those Receiveconnectors, because they always get overwritten by the "Email policy integration".
I haven't found a way where to apply Remote IP Ranges via Forefront TMG console for a SMTP Route, may that isn't possible?
"Remote IP Ranges via Forefront TMG console" -> that I don't think it is possible.