IMHO, telnet is the best tool for troubleshooting NDRs. This usually tells me everything I need to know: Telnet host 25 Ehlo mail.fluke.com Mail from: [EMAIL PROTECTED] Rcpt to: [EMAIL PROTECTED]
Agreed, if the host is a forwarder then there is not much you can tell (ie. Error 552 or 553), unless the host it is forwarding to has 25 open to the internet and you know the server name. You *could* turn up smtp interface logging on your IMS for a brief period of time. You should then start seeing relevant messages in the event logs. If you turn up smtp protocol log, you will start to see log files in the imcdata\log directory. Search the internet for SMTP Reply and Error Codes, print out 100 copies and use them as wallpaper. If anyone asks you about it, recite the codes and meanings like Dustin Hoffman in the Rainman. This will decrease your workload by 25%. -----Original Message----- From: Bob Peitzke [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 5:55 PM To: MS-Exchange Admin Issues Subject: Troubleshooting NDR's Lately we've had more NDR's than usual. I don't see any relevant messages in our E5.5/SP3 server event logs. I've been using telnet and nslookup to try to test messaging to the destination mail servers independent of ours. I could use some advice on using such tools or other, and on troubleshooting NDR's in general. What tests are meaningful. etc. For instance some mail servers hide behind smtp forwarders, and I'm not sure who to try to connect to. Has anyone got any helpful advice in this area? TIA - Bob Bob Peitzke Information Systems Manager Sander A. Kessler & Associates 2850 Ocean Park Blvd., Suite 200 Santa Monica, CA, 90405-6200 [EMAIL PROTECTED] List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
