FE to BE SMTP Connector relationship best practise (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Message Routing



Message

elementaljd -> FE to BE SMTP Connector relationship best practise (15.Jan.2012 9:33:42 PM)

Hi experts,

I have an Exchange 2003 FE server and BE server.

Our mail is spam filtered and sent to the IP address of our FE server where it is picked up. The FE server via smarthost sends mail to our ISP for delivery.

My question is this:

What is the best practice for SMTP connectors between the FE and BE?

Currently, I have it setup as follows.

Connector 1: "FE to BE"

Routes mail for address space ourdomain.com to the IP of our BE server. Attached to bridgehead FE.

Connector 2: "BE to FE"

Routes mail for address space "*" to the IP of the FE server. Attached to bridgehead BE.

Connector 3: "FE to ISP"

Routes mail for address space "*" to the IP of our ISP's smarthost. Attached to bridgehead FE.

It seems over complicated and sometimes we get looping issues with AD groups. Is there a fix for this?

Many thanks.



uemurad -> RE: FE to BE SMTP Connector relationship best practise (15.Jan.2012 11:24:07 PM)

Please explain your reason(s) for sending mail through the FE instead of directly in and out of your BE.



elementaljd -> RE: FE to BE SMTP Connector relationship best practise (15.Jan.2012 11:35:02 PM)

Because the FE server is in the DMZ and has two interfaces. It'd be a bigger job to make our exchange server handle the mail routing. FE also already has web services pointing to it and RPC over HTTPS etc etc.

Is there any way to get this to work in its current form?



elementaljd -> RE: FE to BE SMTP Connector relationship best practise (16.Jan.2012 1:53:38 AM)

OK, so I've eliminated the FE server however when I send an outside email to a distribution group I get this error message and theres not a lot on the net about it:


AdineKirnberg

14110E

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 290
Date: 16/01/2012
Time: 4:31:12 PM
User: N/A
Computer: EX-FE
Description:
A non-delivery report (reason code unable-to-transfer and diagnostic code loop-detected) is being generated for message C=US;A= ;P=OFFICE;L=EX-FE1201160630590716. It was originally destined for DN:CN=TESTGROUP,CN=RECIPIENTS,OU=OFFICE,O=MAIN OFFICE§ (recipient number 1), and was to be redirected to . [MTA DISP:ROUTER 11 136] (12)

For more information, click http://www.microsoft.com/contentredirect.asp.



uemurad -> RE: FE to BE SMTP Connector relationship best practise (16.Jan.2012 8:08:01 PM)

quote:

I've eliminated the FE server
Eliminated from the routing, or eliminated from the Exchange Organization?

If eliminated from the routing, explain what you changed. The simplest configuration has your BE using a Connector for all Address Spaces using DNS. Your Recipient Policy names your own Email domain and states that your Exchange Org acts authoritatively for it.



Page: [1]