Sending mail between internal mail servers on different domains

We have to domains setup in our organization and (for instance).  Obviously has been setup for a while and everything is functioning good. works for the most part....I can send and receive mail from another outside domain and I can send mail to but i cannot receive from it.  When I try to send to from I get this error message:

Your message did not reach some or all of the intended recipients.

      Subject:      test
      Sent:      11/03/2008 5:53 PM

The following recipient(s) could not be reached: on 11/03/2008 5:52 PM
            The e-mail system was unable to deliver the message, but did not report a specific reason.  Check the address and try again.  If it still fails, contact your system administrator.
            < #5.0.0>

Now I know some of that looks funny because our email server is scweb-email not scweb-web so I'm not sure about that either.
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.

Firstly i would recommend you to perform a message tracking and check where these messages are going to.

Secondly, please do tell me if there a smart host located on the server SMTP Virtual Server.

Thirdly, perform a telnet test from server to server and see if the mail goes through.

Are these both servers part of same Administrative Group (for example First Administrative Group) or is it part of separate ones ?
red24698Author Commented:
Well i think i see the problem after your first suggestion....when i track a message from to it goes to the webserver and not the email server and bounces back....but like i said it works fine from the outside....even if i send a message from to and then just reply to that message it still goes to the webserver rather than the email server
Now, your answer lies in the the very second solution i offerred.

Secondly, please do tell me if there a smart host located on the server SMTP Virtual Server

Open Exchange System Manager - Organization - Administrative Group - Servers - Your Exchange server - Protocols - SMTP - Default SMTP Virtual Server - properties - remove the webserver entry mentioned on the first page and select use DNS check box.

You may be required to restart SMTP Service after this.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

red24698Author Commented:
I checked it and it was already set to use dns and there was no smart host listed
Can you attach a screen shot please (I would want the particular tab which talks about smart host setting of SMTP Virtual Server)

Also, do we have any SMTP Connector created on Exchange server ?

red24698Author Commented:
Ok here ya go I think I took a picture of the right screen, and you can see the connectors folder in the background of it
Great, this SMTP Connector does not have the local bridgehead server configured ?? Not sure why you have not added there ??

"Can you attach a screen shot please (I would want the particular tab which talks about smart host setting of SMTP Virtual Server)"

Could you please provide screen shot for the default SMTP VS as asked above.

Thanks for providing such quick response.
red24698Author Commented:
Sorry i couldnt find the option you were talking about under the default smtp so I guessed at what you is a shot of the default smtp if you can tell me where to look from there...also i added the bridgehead while i was there....
"On the Delivery tab, click Advanced to open the Advanced Delivery dialog box."

Screen shot for this, sorry i had presumed that you would know. :)

red24698Author Commented:
No ya go...and thanks for all the help!
Technically speaking your SMTP Connector is done perfectly (except i have not checked the address space - which should have only * in it)

Secondly, your default SMTP VS looks also good.

Is there any Third-Party Application on the Exchange server.
You may want to restart SMTP and Routing Engine service on Exchange box once these changes / settings are verified.

red24698Author Commented:
Only third party are symantec and backup exec but they have been on there for a while and the server can send to everyone else fine just not to domain B......
red24698Author Commented:
oops sry by domain B i meant
red24698Author Commented:
New Info: Now I no longer get that error message....i found out i had pop installed on the webserver which made no sense because we have a email server so i uninstalled that and now when i send an email from to it just gets stuck in the queue of the server.....hope this helps some....
Gets stuck in which queue ??? Whats message tracking telling you ??

I just realised that your Exchange server is not part of this Exchange organization - is that the case ?
red24698Author Commented:
Right they are on 2 seperate machines on 2 seperate domains with 2 seperate organizations...but they are all on the same internal subnet and router.

Its the queue of the server when sending to the server.  I will attach a screenshot of the tracking center...this is as far as it gets....
I guess the thing that gets me the most about the situation is that i can send from to just fine but i cant send to or even reply to when i just received a message fine
Well, this should be as simple as buying a beer on the street.

Create a new SMTP Connector with address space and at the smart host add the ip address of the Exchange server of Restart SMTP service.

Now, tell me if there is any problem.

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
The track states simply that it does not know where to send the messages. So by creating this new smtp connector and providing it with the Exchange server of we should be able to provide it the route.

Hope i made myself clear. :)
red24698Author Commented:
WOOOOOOOOOOOOOOO its works...thanks so much for you help!
Glad to have helped you. Njoi.
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
Email Protocols

From novice to tech pro — start learning today.