Discussion Locked

Bounced E-mails with no explination

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here is the issue that I have been facing for some time now. We are running an Exchange Server 5.5 on our system with service pack 4. We have been having trouble sending mails to 1, and only 1 ISP. We host our domain on our server. The ISP that we are having difficulty with is a part of AT&T. When we send messages to the ISP it returns:

c=US;a= ;p=XXX, Inc.;o=XXX?XXX;dda:SMTP=test@XXXXXXXX.XXX; on 7/24/2001 12:51 PM
Unable to deliver the message due to a communications failure
The MTS-ID of the original message is: c=US;a= ;p=XXX, Inc.;l=XXX_XXXX-010724164937Z-1279

As you can see there is no NDR code with this bounced message. Everyone in the company that tries to send there has this issue. Using NSLOOKUP toolfrom the ISP to our server, the mx record is perfect. All the .dll files have been updated correctly. What is being missed, and is there any solutions??

Thank You

8 replies

by techdictator

A little bit more information is needed. What communications is setup between the mail server and the IPS. (Media, Firewalls, Proxy, etc) and how is the mail server setup to use this. Has it ever worked? What changed since it was working? I await your response.

by techdictator

Here is an article about IMC not functioning properly if the outbox folder is missing (Q147922)
http://support.microsoft.com/support/kb/articles/Q147/9/22.asp?LN=EN-US&SD=gn&FR=0&qry=Unable%20to%20deliver%20the%20message%20due%20to%20a%20communications%20failure%20&rnk=2&src=DHCS_MSPSS_gn_SRCH&SPR=ECH

Another thought, if you are using some kind of dial up connection (Analog or ISDN) Anything that isn't permanently connected you could get an error as well. Here is an article on that (Q242961)

http://support.microsoft.com/support/kb/articles/Q242/9/61.ASP?LN=EN-US&SD=gn&FR=0&qry=Unable%20to%20deliver%20the%20message%20due%20to%20a%20communications%20failure%20&rnk=6&src=DHCS_MSPSS_gn_SRCH&SPR=ECH

by techdictator

Quick thought, if you're running Novell BorderManager as your proxy/firewall are you running clntrust on the server attempting to get through?

by techdictator

Aside from the fact that it's a bad idea to go around your firewall like you described, that doesn't sound like that's your problem. Here's a thought, what is listed as the exchange server's default gateway? It should be the router that's connected to your ISP. Also, if you leave the exchange server where it is, you need to make sure forwarding is disabled and packet filtering is enabled and allow only port 25, and make sure the IMC is configured to not allow relaying, otherwise you may be used by someone to deliver spam. It has now become part of your firewall. I would suggest moving it back behind the firewall. If you need a relay, set up another machine outside the firewall in your DMZ that is locked down tight.

by trupit

The only thing that has changed with this is that a trust relationship and directory replication was set up with another NT server running Exchange 5.5. There is a Novell firewall and proxy, but those have not been changed and have been running allalong with this server, and there was never a previous problem with this.

by trupit

We actually added a second NIC to the Eschange server so that it can reside outside the Firewall as well. So I don't think the Firewall is really an issue anymore.

This discussion is closed to new replies.