Exchange 2003 Mail delivery issues (SMTP Smart Host / Relay)
I found a couple of similar posts on here but none that helped. Hopefully someone can give my tired brain a hand!
Summary: Exchange 2003 server. Previously working until issues which occured yesterday (with no apparent cause... no one using the server, no patches / updates applied, event log clear etc).
Exchange was set with an SMTP Virtual Server and an SMTP Connector pointing to the schools external SMTP feed (Smart Host SMTP with RM/SWGfL).
No major configuration changes for x-amount of months, worked perfectly!
Issue: SMTP became corrupt. Worked through MS KB Article 938673 which looked like a perfect fit.
The hotfix cured the event log errors but eventually led to me having to uninstall SMTP via control panel and re-install, which in turn eventuall led me to having to reinstall exchange and service packs (as in disk in and reinstall over the top to fix errors etc).
Current state of play is that I can't send or receive email at all.
I'm getting MTA and x.400 event log errors (9318 and 290) cycling through the event log, yet I can't find anything obvious wrong with the installation.
290: A non-delivery report (reason code unable-to-transfer and diagnostic code unrecognised-OR-name) is being generated for message C=us;A= ;P=My School;L=MSEX010911041721140715. It was originally destined for C=us;A= ;P=MySchool;O=Exchange;DDA:SMTP=me(a)myschool.la.s ch.uk; (recipient number 1), and was to be redirected to . [MTA DISP:RESULT 16 136] (12)
I've tried creating new SMTP Virtual Server and Connectors with no joy. The Exchange BA and Troobleshooter don't kick up anything that looks immediately related.
9318: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 6, Windows 2000/MTA error code: 1722. Comms error 1722, Bind error 0, Remote Server Name MS2K04 [MAIN BASE 1 500 %10] (14)
There are decent backups available to start a proper disaster recovery / full server reinstall, but it's frustrating - I don't want to reinstall a whole server just for what looks like a transport issue?
Does anyone have any ideas?