All mail stuck in 1 queue

Hi, thanks for any help in advance.

My setup:
we have 1 exchange server, that uses 2 smtp virtual servers.  One of them (SMTP1) routes all internal mail to the outside and recieves all mail.  The other one (SMTP2) recieves mail from our pop users on a different port (ie not 25) and sends mail out.  The default smtp connector shows SMTP1 as a local bridgehead.  This has worked fine for months.

Recently we had to switch external domain names for the exchange server.  I made all the changes I could think of, but not everything is working correctly.

Now, all mail received by SMTP2 gets stuck in its queue, but all in the same line item.  It says 'Default SMTP connector - _3oiasfpo8ajw4p984fa9ij(SMTP Connector - Remote delivery)' and then xx messages, where xx is the amount stuck in queue.  It doesn't have each email listed out separately, by domain, the way I've seen it before.  I can manually cut and paste the emails out of the SMTP2\Queue folder and into the SMTP1\Pickup folder, and it sends them right out.  SMTP1 works just fine.

I have not yet had the ptr record updated with the new domain name, so anything doing a reverse lookup might be having problems, but that would be across both SMTP servers, and I went ahead and changed the external name for SMTP2 to read 'mail.olddomain.com' to match the ptr record w/ the ISP, and that didn't change anything.

When I move the mails out of the SMTP2\Queue folder, the queue item  'Default SMTP connector - _3oiasfpo8ajw...'  still shows that it has the same amount of mails waiting to be delivered, but if I enumerate them, it shows them all to be blank (although they still have the original file sizes).  When I then select 'Delete All Messages (No NDR), it removes them, but stays in the queue showing 0 messages and 'retry'.  If I force connection, it switches to active for a minute, then back to 'retry'.

I have not yet tried to create an SMTP3 w/ the same config as SMTP2, and then disable SMTP2, but I will do so if necessary.  EDIT:  I created an SMTP3, deleted SMTP2, gave SMTP3 all of the settings from SMTP2, and it's doing the same thing.

Please help me figure out why my mails are getting stuck in SMTP2's queue.

Thanks.
robpendleyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

robpendleyAuthor Commented:
Adding SMTP2 (now SMTP3) as a local bridgehead to the SMTP Connector fixed it.  It was not set this way before, though, so I still don't understand what happened.
0
f_umarCommented:
now smtp3 is configured as a local bidge head server so it is using smtp connector to send mails out for external users.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robpendleyAuthor Commented:
Thanks,
I understand that, but I don't know how SMTP2 used to work without being a local bridgehead, yet now it won't work without being a local bridgehead.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

f_umarCommented:
what are u usning to send emails dns or smart host?
0
robpendleyAuthor Commented:
DNS
0
f_umarCommented:
internal DNS with forwarders or External DNS?

please take a look on the following for Understanding SMTP and Exchange Server 2003
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TransnRouting/0fe7e642-daec-4b1e-b9a9-836e38f2a776.mspx?mfr=true

0
robpendleyAuthor Commented:
Internal DNS with forwarders.  It's Exchange 2000, not 2003.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.