Publish SMTP for TMG 2010 with Edge Subscription
-
Saturday, September 25, 2010 8:12 PM
In a test network, I recently introduced email protection to an existing TMG 2010 server. I appear to have successfully created the edge subscription, following directions in the Technet Library. However, a publishing rule existed, which directed inbound SMTP traffic to the hub server. After creating the edge subscription, SMTP traffic continued to be routed to the hub server, as opposed to being intercepted by the TMG server. Deleting the publishing rule simply caused SMTP traffic from the Internet to be rejected by TMG.
I got the impression that using the Email Policy Wizard and answering the prompts correctly would be enough to configure TMG as needed. It created the System Policy rules that appear to be needed as well as the 2 needed SMTP routes. Do I need to create a new publishing rule, or should this be working provided I configured it correctly via the wizard?
Thanks.
All Replies
-
Tuesday, September 28, 2010 9:48 AMModerator
Hi,
Thank you for the post.
To configure an Edge Subscription, you can refer to the following steps:
1.Use the E-mail Policy Wizard to allow Edge traffic on Forefront TMG.
2. Create the subscription files with a click: “Generate Edge Subscription Files”.
3. Import the files to the Exchange Hub server,
If the above not work, please refer to: http://technet.microsoft.com/en-us/library/ff849725.aspx
Regards,
Nick Gu - MSFT -
Wednesday, September 29, 2010 2:15 AM
Thanks. I am going to remove the subscription and start over. When I set up the subscription, the TMG Managed Control service was stopped and wouldn't start, because of Exchange 2010 SP1:
I installed the update rollup that fixes the problem, so maybe I'll have better luck if I try again.
- Marked As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Thursday, September 30, 2010 1:58 AM
-
Thursday, September 30, 2010 3:20 AM
I just removed the original edge subscription on the hub server, then generated a new one and imported it to the hub server and the problem is solved. I guess the fact that TMG Managed Control wasn't started the first time must have caused the problem, because everything was done the same way this time.
Cheers.

