Solved

Smart Host problem - 3x Back end servers, no FE server

Posted on 2008-10-17
3
468 Views
Last Modified: 2013-11-15
We have three back-end Exchange 2003 servers, all SP2. There is no front-end server.

Two are in one site - we'll call those London1 and London2. The other is at a remote site, we'll call that Remote1.

Up until today, London2 and Remote1 have London1 configured as a Smarthost. This then send's e-mail using DNS lookup. Today we setup with a 3rd party mail filter, Messagelabs. I configured London1 to relay all e-mail via Messagelabs (I.e. I configured messagelabs as a smarthost under the smtp virtual server on London1).

Since adding the smarthost, some of the e-mails sent from mailboxes on London1 to mailboxes on the other servers end up in a queue called remote1.ourdomain.com and london2.ourdomain.com and then move quite quickly (couple of minutes) to the 'Messages queued for deferred delivery' queue.

If I take the smarthost out of London1, mail flows around the company fine.

I want to use the smarthost for all mail that leaves the organisation but I also want mail to flow properly between my back-end servers. I think the solution might lie in routing groups and connectors but I'm not really sure what I'm doing with those.
0
Comment
Question by:tlcsupport
  • 2
3 Comments
 
LVL 12

Expert Comment

by:aa230002
ID: 22762068
How many Routing groups you have and how these servers belong to these routing groups?
You dont need to give smart host on all servers our your organization. You just need to define routing groups and then create routing group connectors between them for mail flow.

On London1 server, i would recommend you to create a SMTP connector with Address Space * and then send all mails to 1 single IP of MessageLabs using this SMTP connector rather than giving the smart host on SMTP virtual server properties.
0
 
LVL 1

Author Comment

by:tlcsupport
ID: 22766235
All 4 servers are in a single routing group. Perhaps this is the problem.

If I create a connector with the address space of *, internal e-mail destined for the other servers attempts to go out via the connector.
0
 
LVL 1

Accepted Solution

by:
tlcsupport earned 0 total points
ID: 23485019
Having removed Sophos Puremessage, the problem resolved. Very strange behaviour. We've since replaced the offending Exchange server and installed Puremessage onto it and do not experience the same problems.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In this article, you will read about the trends across the human resources departments for the upcoming year. Some of them include improving employee experience, adopting new technologies, using HR software to its full extent, and integrating artifi…
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question