Discussion Locked

Added Exchange domain can't receive mail

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I cannot receive email on a new domain I added to my Exchange 2000 server.

I have a Win2k server w/SP4 and Exch2k SP3 installed. My users from the original domain, domain1.com, have always been able to send/receive email without issue.

Recently, we acquired a company which is going to merge with our mail server. They own domain2.com.
In an effort to setup a second domain on our Exch Server I did the following - I created:

-new storage and stores for domain2.com
-global address entry
-recipient policy for domain2.com, modified it to refelct the correct storage location for the mailbox store, ensured the box was checked "the exchange organization is responsible..etc"
-domain2.com users via AD, then pointed them to the domain2.com store.

I control my dns records for domain1.com and domain2.com via zonedit.com; mx records are correct and verified via nslookup. (pointing to same ip as domain1.com)

domain2.com users can send without issue.
However, when trying to send email to jo@domain2.com from the outside world I receive the error message:

:
123.12.123.123 does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for jo.domain2.com
Giving up on 123.12.123.123.
-OR-
"Got an unknown RCPT TO response:"

I have done a little work attemping to setup a relay for domain2.com within the SMTP virtual server.
I have also tinkered with creating an SMTP connector with domain2.com in the address space, allowing routing to that domain. Both attempts: no luck.

Hope that was enough info. Any ideas helping me allow domain2.com to receive outside e-mail?

---
"I drank what?"
-Socrates

6 replies

by cg it

humm Val Kilmer said that line in a movie....

Question: How is the domain name space setup for the domains? Is it 2 seperate domains not within the same forest?

by geekinz

There is no second domain setup within the domain1.local AD schema.

I have added domain2 as an OU to domain1.local, then created users. (domain1.com and domain2.com were added into Exchange's default receipient policy).

I added domain2.com to the local-AD DNS so their intranet and mail.domain2.com can be accessed internally.

by ariston

Here's an option, if you know that the DNS records are proper, under the AD user accounts, add user@domain2.com as an email address in the list. When mail gets routed to your Exchange server addressed to user@domain2.com, it will find a match in the AD user profile and deposit the mail in their box (which was configured when the user was added to the AD in the first place.)

Give that a shot and see if it works.

Ariston Collander
ariston@coxcomputer.com

by geekinz

Ariston,
The users in domain2.com already have addresses for domain2.com (as defined in the policy); or are you talking about something else?

by geekinz

UPDATE: Ok, I am not getting the "Remote host said: 550 5.7.1 Unable to relay" anymore (that was fixed). However, now my emails are staying not being delivered to the end user. I can see messages in the mailbox store.

?

by bbae

What about adding xxx@domain1.com email address to all users xxx@domain2.com? Because of AD, without a default email address, users can't receive any email from outside.Hopefully it works.
Good luck.

This discussion is closed to new replies.