climberboy
asked on
Exchange 2003 only recieving some incoming messages.
Hi Experts!
Now that I have my exchange server correcting sending and receiving mail from other SMTP domains, I am having another problem. I have the following MX records:
0 @ exchange.vs-us.com TTL 3600
10 @ smtp.secureserver.net TTL 3600
20 @ mailstore1.secureserver.ne t TTL 3600
Some of my user's mail is going to my exchange server, which is priority 0. The rest is going to the "backup" server hosted by GoDaddy. I cannot figure out why, and the split seems to be pretty arbitrary.
Any help would be appreciated.
Now that I have my exchange server correcting sending and receiving mail from other SMTP domains, I am having another problem. I have the following MX records:
0 @ exchange.vs-us.com TTL 3600
10 @ smtp.secureserver.net TTL 3600
20 @ mailstore1.secureserver.ne
Some of my user's mail is going to my exchange server, which is priority 0. The rest is going to the "backup" server hosted by GoDaddy. I cannot figure out why, and the split seems to be pretty arbitrary.
Any help would be appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It might cause problems with some outgoing messages, since ISP's like AT&T and AOL routinely check the RDNS and reject email that doesn't comply. The reason you're getting that response is that your reverse DNS record is currently pointing to 216-60-35-249.ded.swbell.n et. It should be pointing to your own email host name - exchange.us-vs.com. You need to go to wherever the external DNS zone is (godaddy, I guess) and remove that PTR record and add on that points to the correct host name.
ASKER
Reverse DNS is correct... The gateway IP address (216.60.35.194) is what shows when sending through Exchange, and there is a PTR record there for mail.vs-us.com. We should be in good shape.
I'll post again if I still need more help with the split destinations issue.
I'll post again if I still need more help with the split destinations issue.
ASKER
Hypercat,
Thanks again. Everything Kosher... had both IPs on the DNS entry.
Have a great day!
Thanks again. Everything Kosher... had both IPs on the DNS entry.
Have a great day!
You, too...No more Exchange problems allowed for you this week - you've had your quota ;-)
ASKER
Along the lines of routing, when I do diagnostics on vs-us.com from mxtoolbox.com, the primary server says that reverse DNS is not configured properly. Any idea how to fix that? I'll bet that will cause problems too.
Thanks,
Eric.