Can't send/recieve emails.

[rotaman]

dear all,


We have a dilemna,

As of this morning we can not send emails. Each time we try to send a mail, we get the following error:

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

Subject: TESTER
Sent: 17/01/2005 12:37

The following recipient(s) could not be reached:

'xxx@gmail.com' on 17/01/2005 12:37
Unable to deliver the message due to a communications failure
The MTS-ID of the original message is: c=US;a= ;p=ITX;l=ITXPAREX1-050117113727Z-14

I have checked around, our event log shows the following errors:

Event ID: 12006
L'erreur 80004005-F2000235 s'est produite lors du traitement du message <3A67475B44EC$2DF499B3$0a5738f4@aol.com> provenant de 'xxx xxx'. Le nom du fichier archive est 'DD5BDHBV'.

Event ID: 4117
Une erreur a été retourne par le logiciel de messagerie utilis par le service Messagerie Internet pour traiter les messages sur le serveur Microsoft Exchange. En conséquence, le message dans le fichier spoule DD5BDHBR n'a pas pu tre remis. Le message a été déplacé dans le répertoire IMCDATA\IN\ARCHIVE.

we are running Exchange server 5.5 SP4 on WinNT 4.00.1381.

We have looked on the web for help, microsoft lists an issue concerning the 4117 and 12006 errors, but we are wondering if installing more updates will fix the problem. We are also wondering about using the eseutil.exe utility, as it takes hours to perform, and we have users waiting to use their emails.

Thanks for any info you can send us

 

[rotaman]

Please, please reply.

Additional info: All outgoing mail is sent to a unix server, and we can send mail through the unix server, so it is definitely a problem with Exchange.

Help us!

 

[rotaman]

oh yes, and when we try to send out an email, the error:

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

Subject: TESTER
Sent: 17/01/2005 12:37

The following recipient(s) could not be reached:

'xxx@gmail.com' on 17/01/2005 12:37
Unable to deliver the message due to a communications failure
The MTS-ID of the original message is: c=US;a= ;p=ITX;l=ITXPAREX1-050117113727Z-14"


comes back immediately. There is no lag whatsoever.

And we are not blocked by any spamfilter etc, and DNS is a okay.

HELP!

 

[dennisbbb]

1) is your Internet Mail Service dead in the water?
Restart it.

2) If it failed to start, delete it, and re-add it back.

3) Since you are relaying from Exchange, doublecheck connection by going to the command prompt and type in "telnet Unix# 25" from your Exchange server.

 

[rotaman]

The IMS is running, we have even restarted the server. We have also done the Telnet from the exchange server with success.

priv.idb is 28GB, so we are currently defraggin that with the eseutil util. Next we have a couple post-SP4 updates we can try, but that's all we have for now.

Thanks,

 

[dennisbbb]

stop IMS and clear out all queue files in in/out folders located in exchsrvr/imcdata/, then restart it again.

 

[rotaman]

Dear dennisbbb,

there are no queue files in any of those directories.
We did try to delete queue.dat, still no success.

thanks for your help,

 

[dennisbbb]

From the error, it is very obvious it is a DNS problem. Either your Unix cannot send out, or your Exchange cannot relay to the Unix. Is Unix preventing relay?

 

[adonis547]

Dennisbbb:

Sending from the unix box works fine. The mailserver log on the unix box, is not even registrering connection attempts from the exchange server.

I can do a `telnet unixserver 25` from the exchange server, and it works fine. I can also do a `telnet exchange-server 25` and send a mail without any problems.

nslookup -type=mx whatever.domain works as well. We've been running with this setup for a while now, and all of sudden it no longer works.

Any input would be greatly appreciated.

 

[rotaman]

anyone?

 

[zbnet]

The smarthost is obviously contactable from the Exchange server necause you've tested this with your manual telnet, so it really looks like an Exchange issue.

Has someone messed around with your IMS settings?

If you're sending all your outgoing email to the unix server (smarthost), then this ip address should be in the "Forward all messages to this host:" box on the Connections tab of the IMS. Someone might have changed the settings a long time ago, but only a recent stopping and restarting of the IMS service kicked the change into use, perhaps?

 

[rotaman]

Thanks to all for your help.

We ended up by deleting the IMS connection and recreating it. For some reason this solved our problem.


Thanks!!