send email OK.But can not receive email with 1 domain in Exchange 2003 1

[rbby2003]

I can send email but not receive email in Exchange 2003, which is also a DNS server running Windows server 2003 standard edition. I have MX record for this domain name. For a different domain I don't have the problem, I mean for the other domain name I can both send and receive email, no problem. Both domain names are using the same public IP.

What can I do to solve the problem?

Is there something in Exchange 2003 I can allow only send or only receive for a specific domain?

Thanks.

 

[Xanaxo]

You must configure your Exchange server to accept mail for that domain. You need to add the domain to the recipient policy. If you want to specify certain users to have one email address while other have a different one, then you will have to create a new policy with an LDAP filter that will apply to only the users that you want to have a particular address. You can filter on a user attribute such as "Company" or a "Custom Attribute". The default policy will apply automatically to any object that needs a mail address that was not already configured by a higher priority policy.

Read the following to do this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;249299#appliesto

Steven Parent [MSFT]

 

[rbby2003]

That's it. Thanks, Xanaxo. I added the recepient policy and I can receive now. Yeah, I can send and receive email now.

There was a small trick that for the 2 domains on the same Exchange server, I could sent and receive email to each other although at that time I had problem with 1 domain receiving email from hotmail. That is tricky because it appears that everything is fine if you just send email to the domain on the same Exchange to test email.

Can someone explain this please?

 

[Xanaxo]

When you sent that message internaly did you choose the user from the GAL or type in the broken SMTP adderss into the To: line?

If you do not address it directly to that SMTP address, it will use the x.400 or primary SMTP internally.

Since it did not work from External, that tells me it wasnt setup right then either. So either way you look at it, this was and is the fix.

Glad I was able to help.

Steven Parent [MSFT]