Link to home
Start Free TrialLog in
Avatar of Justin Durrant
Justin DurrantFlag for United States of America

asked on

5.4.0 NDRs when sending to one domain (nextel.blackberry.net)

Here is the deal.. I have a single Exchange 2003 server on Server 2003 that is also the DC and DNS server for a small business. The company just got a few BlackBerrys through Nextel. The problem is we cannot send to the blackberry addresses from inside the internal network. The domain we are sending to is user@nextel.blackberry.net. My end goal is to setup a Exchange 2003 contact to forward any messages coming into our user1@domain.com to the user1@nextel.blackberry.net address.The exact NDS is as follows:

Your message did not reach some or all of the intended recipients.

Subject: test
Sent: 5/3/2005 9:58 AM

The following recipient(s) could not be reached:

  John Doe (Blackberry Email) on 5/3/2005 9:58 AM
  The destination server for this recipient could not be found in Domain Name Service (DNS). Please verify the email address and retry. If that fails, contact your administrator.
  <emailserver.domain.com #5.4.0>

I can email any otherexternal domain fine. I don't understand why this one is not working. I don't know of any other name.domain.com to try (not sure of that even matters). I tried to send to the nextel.blackberry.net domain from many other locations (work, school, ect.) and it works fine. I did a NSLOOKUP at work and I get a reply, yet the email still does get delivered when I send test messages from here:



Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\justin>nslookup -q=mx nextel.blackberry.net
Server:  server.domain.com
Address:  192.168.8.5

Non-authoritative answer:
nextel.blackberry.net   MX preference = 10, mail exchanger = mx01.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx02.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx03.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx04.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx05.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx06.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx07.bwc.na.blackbe
rry.net
nextel.blackberry.net   MX preference = 10, mail exchanger = mx08.bwc.na.blackbe
rry.net

mx01.bwc.na.blackberry.net      internet address = 206.51.26.128
mx01.bwc.na.blackberry.net      internet address = 206.51.26.154
mx01.bwc.na.blackberry.net      internet address = 206.51.26.134
mx02.bwc.na.blackberry.net      internet address = 206.51.26.129
mx02.bwc.na.blackberry.net      internet address = 206.51.26.208
mx02.bwc.na.blackberry.net      internet address = 206.51.26.135
mx03.bwc.na.blackberry.net      internet address = 206.51.26.130
mx03.bwc.na.blackberry.net      internet address = 206.51.26.214
mx03.bwc.na.blackberry.net      internet address = 206.51.26.136
mx04.bwc.na.blackberry.net      internet address = 206.51.26.131
mx04.bwc.na.blackberry.net      internet address = 206.51.26.215
mx04.bwc.na.blackberry.net      internet address = 206.51.26.137
mx05.bwc.na.blackberry.net      internet address = 206.51.26.132
mx05.bwc.na.blackberry.net      internet address = 206.51.26.223

C:\Documents and Settings\justin>


I few people recommended I setup a custom SMTP connector to route email destined to nextel.blackberry.com through my ISP SMTP gateway (smtp.popp.net). I did that per the instructions below, but still no luck.

http://www.amset.info/exchange/smtp-connector.asp

Any ideas?
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Justin Durrant

ASKER

Yes I get the same error after setting up the SMTP connector. However I not sure how to actually verify the custom SMTP connector is actually being used. The NDS is genrated from our Exchange server. I did not try a telnet test. Please give me details about that.
These are instructions on doing a telnet test.

http://support.microsoft.com/?kbid=153119

Obviously this will bypass any SMTP Connector that you might be using and try and connect directly.

The way that I check whether the SMTP Connector is working is to see if it is listed in queues in ESM. As a test you could change the server that it trying to connect to, and put an invalid IP address in to the box instead. This will force the messages to queue instead of being delivered.

Simon.
Hey Simon,

nextel.blackberry.net fails

C:\Documents and Settings\justin>telnet nextel.blackberry.net 25
Connecting To nextel.blackberry.net...Could not open connection to the host,
port 25: Connect failed



mx01.bwc.na.blackberry.net  is ok

220 mx01.bwc.na.blackberry.net ESMTP Sendmail 8.13.1/8.13.0; Tue, 17 May 2005 00
:12:17 GMT

There seems to be a problem with the nextel name somehow. Is there a way to tell exchange to connect to the mx record when send mail to the nextel domain?
Have you asked Nextel whether there is a problem?
You could redo the SMTP Connector to point at one of the MX servers directly. However if you did this then you should enter multiple servers so that there is some redundancy.

Simon.
I have not. Like I said, it works everywhere else. I will try and point to the mx records directly and go from there.


Ok,

I added the following to the "Forward all mail through this connector to the following smart hosts":

[206.51.26.128],[206.51.26.154],[206.51.26.134]

In the address space tab I have:

nextel.blackberry.net

Still no luck....

Justin
Sorry for being unresponsive, I had an Exchange migration go badly wrong on me and it has taken almost 2 days to fix.
I see that Vahik has made some suggestions in the other thread. You need to see what he comes back with to see whether that gives a clearer indication of the problem.

Simon.
Thanks

Hope all is well with your migration.
Ok.. The POP3 test works from Outlook Express on the Server. It must be a problem with Exchange.


Thanks again for sticking with me.. Too bad I never was able to get the actual issue resolved. :)