why email can not send to sepcefic domain

human1900
human1900 used Ask the Experts™
on
Why can not send email to sepcefice domain as domain.com , I chaecked user email it is verfing or it is working but I can not send to it,  How I can fix this issue in exchange server 2003 .
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Awarded 2009
Top Expert 2010
Commented:
Do you receive a NDR message?

Have a look at this FAQ from alanhardisty: http://www.it-eye.co.uk/faqs/readQuestion.php?qid=2
Commented:
If you have a problem sending to any user on any domain, you will need to verify your Exchange configuration and connectivity including DNS configuration.
If you have a problem sending to a single domain only, or a few domains, while your other mail flows has no problems, them most probably you have a DNS issue.

Make sure your DNS server can resolve the MX records of the target domain.
Commented:
I agree with hkunnana, I think the issues is DNS related - specifically Reverse DNS which some mail servers require.

I suggest that you use the MXToolbox to test for issues.
http://www.mxtoolbox.com/diagnostic.aspx
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Awarded 2009
Top Expert 2010

Commented:
All of this is covered in the FAQ I posted in my first link.

Author

Commented:
How I can Make sure DNS server can resolve the MX records of the target domain.
Awarded 2009
Top Expert 2010
Commented:
This is down the the owner of the target domain if their DNS is incorrect then they need to resolve this, you cannot.
Awarded 2009
Top Expert 2010
Commented:
Have you gone through the FAQ I posted?
Commented:
In answer to your question, you should be able to use NSLookup on your exchange server to ensure that the DNS Server you are using can resolve the MX record.

You just need to set NSLookup to check MX Records

nslookup
set type=mx
<recipientmailserver>

Author

Commented:

I done Checkup for Nslookup it is fine. But when I checked through sit I got this message
Warning - Reverse DNS does not match SMTP Banner
There are some anti-spam folks that require the rDNS (PTR) matches the helo/ehlo.
If the warning you recieved was when you tested your mail server, to remove the warning you need to do either of ther following:
1- Change your masquerade domain to match the PTR record
2- Have your ISP change your PTR record to match your masquerade domain

The masquerade on the SMTP configuration will "mask" the real name of the server and portray as the masquerade name.  Most masquerades are something like mail.domain.com.  The masquerade domain will be presented in the banner and the helo/ehlo communications.

My suggestions is to telnet test from your exchange server to the destination mail server.  Generally, you will see a custom error message that is blocking your mail if your PTR is not sufficient, or if other anti-spam issues exist.  You can follow the instructions above for getting the ip address of the MX record.  Then you can follow the instructions here to do the manual telnet test from your Exchange server  (Important because you may be doing port specific NAT, which would effect your outgoing IP for SMTP):  http://support.microsoft.com/kb/153119
Simon has a page for this as well:  http://www.amset.info/exchange/telnet-test.asp

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial