Discussion Locked

Exchange 2000 can't receive mail

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

Problem:
I can send email to an external email address but when I reply back, no email is ever received.

Background:
I have setup a Windows 2000 Server-SP3 w/Exchange 2000-SP3, domain is test.local
I have a registered domain name (newdomain.com, for example).

My ISP's DNS is pointing to my Exchange box, and an MX record was created for mail.newdomain.com, which points to my Exchange box's IP.

I have modified the recipient policy so that all user's default/primary email address is username@newdomain.com (by default is was set to @test.local)

I created a new (local) primary DNS called newdomain.com and entered in mail as an alias and pointed it to my Exchange box, on the test.local domain. (If that makes sense and not sure if this step is necessary).
Internal email functions perfectly.

Currently, I am running strictly SMTP via port 25.

Problem:
As mentioned earlier, I can send to a yahoo-type address and it comes in as username@newdomain.com. However, when I reply and send back to that address, it doesn't deliver to that user on my Exchange 2K network.

That's the scoop - any questions, fill-in or what not please let me know and any help would be greatly appreciated!

8 replies

by curlergirl

This sounds like a typical DNS resolution problem, but it also sounds like you have done the right thing DNS-wise with your ISP. How long has it been since this was set up? If it's been less than 3 days, it could be a simple propagation problem - it usually takes about 3 days for propagation of new DNS records across the Internet. (BTW, you don't need the local DNS zone for newdomain.com, but if you're going to have it there, it should point to your Exchange server's public IP address.) Theother element that could be a problem would be a firewall of some kind. Do you have one in place? If so, maybe more info about that would help.

by geekinz

Don't know why but my e-mail suddenly started working after aked the ISP to completely delete and re-add my domain. Everything is up and running smoothly.
Thanks to everyone for your help!

by acattr

1. Did you update the default recipient policy in exchange to include the @newdomain.com domain. Your exchange server will reject emails if you don't do this.

Go to the exchange system manager, recipients, recipients policies, default policy,properties, email tab, new, smtp address, under address field put @newdomain.com, hit ok, put a checkbox on it, select it, set as primary, hit ok, hit yes to apply to all users.

2. test your mx records
from anywhere outside your network, use the utility nslookup to make sure your ISP inputed the write MX records. from a command prompt, run nslookup.exe. then type "set q=mx" to query for MX(mail) records. then type your newdomain.com. It should read back the internet name of your mail server.

OUTPUT OF NSLOOKUP BELOW:

C:\Documents and Settings\user83920>nslookup.exe
Default Server: ns1.TechLab.microsoft.com
Address: 10.58.62.2

> set q=mx
> newdomain.com
Server: ns1.TechLab.microsoft.com
Address: 10.58.62.2

Non-authoritative answer:
newdomain.com MX preference = 20, mail exchanger = mx2.activeisp.com
newdomain.com MX preference = 10, mail exchanger = mail.asp.activeisp.com

newdomain.com nameserver = dns12.activeisp.com
newdomain.com nameserver = dns10.activeisp.com
newdomain.com nameserver = dns11.activeisp.com
>

by acattr

if 1 or 2 don't help. Please post the error message a user gets when they reply to you. This will help greatly.

by geekinz

This solution was very helpful in pin-pointing the problem. I discovered that, after running the nslookup, the problem existed outside of my Exchange environment.

by atharaaa

As discussed, You have modified the mail receiving policy which is right. The only issue to me which could be causing problem is that, you had established your own primary DNS and pointed it to the ISP's DNS.
By doing this, you are trying to resolve the hostnames/domain names of the registered domain on the internet through your DNS. Ex. you can ping directly to Microsoft using your primary DNS. The question arises here is, whether your DNS is able to update itself thru your ISP's DNS or not. If this is not happening the addresses are not being resolved hence mails are not reaching your mail server. Check this possibility.

This discussion is closed to new replies.