We help IT Professionals succeed at work.

Email hung in queue on new Exchange 2010 server

Jer
Jer asked
on
Greetings,

I just added a second Exchange 2010 server (typical install) last night.  Since then, all outgoing email to external sources is now being held in queue on the new Exchange server.  I expect that this has to do with a receive connector configuration.  However, I'm not having any luck.

A little extra background...

I just retired my last Exchange 2003 server prior to installing the new (2nd) Exchange 2010 server.  In my test environment, I had both Exchange 2010 servers and 1 Exchange 2003 server and had no issues.  However, upon decommission and removal of the Exchange 2003 server, outgoing email to external addresses broke.

All internal email is working fine and we are receiving external emails normally.  It is just outgoing to external addresses that are impacted.  We have 700 in queue and building.

Please advise if you have any suggestions.  

Thanks,

Jeremy
Comment
Watch Question

Seth SimmonsSr. Systems Administrator

Commented:
is there a send connector?
was all external mail going out through the 2003 server?
Commented:
the new exchange was using the 2003 send connector for external email
just create a new send connector
Commented:
Oops.  Yah.  Meant to say 'send connector'.  I did create a send connector, but it still failed initially.  I think it was due to a conflict with an existing receive connector on the original Exchange 2010 server (new Exchange 2010 server's IP was within the range).  As this second server is not intended to initially handle any email, I probably should have only installed the mailbox role (and management) and added the client and hub roles later.  The sole purpose of this second server is to be an archive mailbox server (getting rid of the PSTs).  However, it will ultimately serve as a backup/failover Exchange server (thus, the client and hub roles).  I was not prepared for this server to manage any email, so it caught me off guard.  With the send connector in place and a couple of the receive connectors disabled, email is traveling to its destination.  However, it is definitely not in a preferred state.  I presume with the natural design of Exchange, I cannot stop the routing of email through the new Exchange server without removing the hub and/or client role?  Yesterday, my priority was to just get the queue on the new server cleared and get mail flowing.  I'm going to dig back into it again this weekend, as I need to have the custom receive connectors to accommodate copiers and other devices that are exceptions to the default rules.
Seth SimmonsSr. Systems Administrator
Commented:
I cannot stop the routing of email through the new Exchange server without removing the hub and/or client role?

correct...but you should build another server first and have the connector send from that server so as to keep this one just for mailboxes
Jer

Author

Commented:
I had the solution.  Just got confirmation.  Was hoping for a better option.