Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2000 unhelpful NDR

Status
Not open for further replies.

jprovett

Technical User
Jan 16, 2002
7
GB
I was wondering if anyone could point me in the right direction ..

Exchange 2K ihas been set up and running quite happily for about 3 months now the problem is if we try to send an email to 3 particular domains it never reaches the destination and come back with this error :-

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

Subject: Test message
Sent: 14/01/2002 07:42

The following recipient(s) could not be reached:

SimonBeasley@centro.org.uk on 16/01/2002 07:49
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<jasmin01.JASMIN.PLC.UK #4.4.7>

I have found an 'explanation' but it doesn't help .. :-

· Numerical Code: 4.4.7
Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message but the action was not completed before the message expiration time occurred. This message can also indicate that a message header limit has been reached on a remote server or some other protocol timeout occurred while communicating with the remote server.
Troubleshooting: This message usually indicates an issue on the receiving server. Check the validity of the recipient address, and determine if the receiving server is configured to receive messages correctly. It may be necessary to reduce the number of recipients in the header of the message for the host to which you are receiving this error. If you resend the message, it is placed in the queue again. If the receiving server is up, the message is delivered.


Can anyone point me in the right direction ?

I personally don't think there is anything I can do - and that the problem is with the receiving server .. anyone else agree ???

Help !!

Jo.
 
Basically we can't send it... We don't totally fail or would get a 5.x.x error. Get the MX for that domain and send it directly via telnet and see if it goes. Dan
Microsoft Exchange Support @ Microsoft
 
Have you downloaded and installed Exchange Service Pack 1? I had similar problems and most of them went away after I installed the SP.

You could also try adding the DNS servers of the destination addresses to Exchange.

Hope this helps.

Gary
 
We are on SP2 - which is where this problem came from in the first place .. it was working ok until we installed SP2 (we were previously on SP1 !)

Thanks anyway

Jo.
 
Did you test a message to the domain via telnet? Dan
Microsoft Exchange Support @ Microsoft
 
I have the same problems, W2K SP2 + E2K SP2, I succeed to send messages through telnet, I've set up a smtp connector to relay.provider.com (which i can telnet btw) and thought this was the solution but it isn't.

The NDR (the 4.4.7 message) comes from the administrator of the local exchange server. When I try to read headers, the mail never left the organisation.

Any help to this weird problem is appreciated

Bart

 
Uh thats not good :)

Check Reapi.dll is it version 6.0.4418.33 or higher?

Another case points to :

Resolved the problem by disabling &quot;Check Inspection State&quot; for the SMTP traffic setting on the firewall.

Firewall a watchguard firebox? Q312415

Hope that helps. Dan
Microsoft Exchange Support @ Microsoft
 
I had the same problem a while ago. My ver. was sp1.
On the SMTP connector i checked the box &quot;send HELO instead of EHLO&quot; and that seemed to solve most of the problems.
I do not know exatctly what other consequences this will have but you might want to try it out. I still use this config under sp2.

RuneT

 
Ok. Since I moved mailboxes from exchange 2000 to another box, by default, the first exchange installed becomes the master within the first routing group, therefore, the old exchange was set as master. It looked like the mail was checking fisrt the smtp of the old exchange. rightclicking the new exchange server ans setting up to master resolved the problem.

Good Luck!!!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top