Mail sending error in certain domains through excahnge server 2003

0 pts.
Tags:
Business/IT alignment
Data analysis
Exchange security
Microsoft Exchange
Microsoft Windows
Networking
Hi all Recently I have installed exchange server2003, and configured outside email also its working fine, I can send and receive mails form yahoo, hotmail, gmail, but some domain I can not send but I can receive mails from these domains. I am getting following error message Your message did not reach some or all of the intended recipients. Could not deliver the message in the time limit specified. Please retry or contact your administrator. <mailservername.com #4.4.7> In my server there is no restriction it is open send and receives for all. What could be the problem please help me on this Thanking you in advance.
ASKED: November 16, 2006  8:41 AM
UPDATED: November 22, 2006  2:47 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi,
Does this happen on all domains except for yahoo, hotmail and gmail or only on specific domains?
Does it happen only when you send large amount of email at once (e.g. some marketing mailing) or even when sending message to single recipient? I had similar issue during email marketing campaigns and it was related to Windows DNS and firewall (Netscreen). I will describe it in more detail if your issue shows up in similar situations.
Do you have extended logging enabled in Exchange? If not enable it and check how the SMTP transmission looks for this recipient.

Regards
Maciek

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Mortree
    Multiple possibilities. First check how long you are allowing for delivery before timeout. Typically you should leave this set to 4, 6,12 hour intervals for when you start getting messages about not delivered on time. Even major ISPs sometimes choke up for a while especially as holiday approach. Shorter timeout don't speed mail. You get this if the target email server is down or does a dial-up Internet connection (unusual but some small businesses might be cheap). Routing errors between your email server and destination server -- you and your ISP would be my first checks. Here certain IPs just aren't pointed down the right wires or get blocked inappropriately. Try pinging the destination email servers. You can use command line NSLOOKUP in interactive mode with type=MX to get DNS mail records for the domains in question. You can get this if DNS is wrong especially if MX (mail records) are out of date or otherwise bad. If the server pointed at is not an email server it won't talk email (SMTP). It might be possible to get this if no MX record exists. However the no MX record usually has a different response message that says no mail server exist. There are couple of new more secure email protocols that use new DNS records, etc that not everyone is set to be compatible with yet. You may also get this if the server at the other end has customized its messages and responses becasue of SPAMMERS. Here I would suspect your server is configured as an open relay (SPAMMER Heaven) and you got onto a blacklist. Some blacklist subscribing servers may fake dropped/interrupted connections, etc. Some blacklist servers don't want to reply "rejected as open relay you filthy spammer" because today's spammer programmers are yesterday's Denial of Service script kiddies & they still have hair trigger tempers. So check "open relay" configuration considerations for Exchange and whether you are on any blacklists (google works to find SPAM blacklists).
    0 pointsBadges:
    report
  • Mortree
    Try pinging the destination email servers from your email server. If no ping then try tracert to find where the IP packets die. Oh and obviously if NSLOOKUP yields no MX records...well maybe the email server doesn't exist. This actually happens a lot if people reply to SPAM or "no reply allowed" mailings. Often the domain is faked if a SPAMMER or even legitimate (e.g. PAYPAL Customer service wants no replies) or stubbed (legimate user but wants to kill email replies and send you to website e.g. PAYPAL).
    0 pointsBadges:
    report
  • Mortree
    Try pinging the destination email servers from your email server. If no ping then try tracert to find where the IP packets die. Oh and obviously if NSLOOKUP yields no MX records...well maybe the email server doesn't exist. This actually happens a lot if people reply to SPAM or "no reply allowed" mailings. Often the domain is faked if a SPAMMER or even legitimate (e.g. PAYPAL Customer service wants no replies) or stubbed (legimate user but wants to kill email replies and send you to website e.g. PAYPAL).
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following