We have an older SQL2000 server running on Windows 2003 that we can't get rid of yet or upgrade to a newer version of SQL due to legacy software. It will hopefully be gone in the next 12 months or so but it needs to keep running for now. It has been running nightly jobs that send out reports via email for years using an exchange MAPI profile via Outlook 2003. The problem is we have moved our users to Office365 and want to shut down the exchange server.
I have setup an SMTP relay on one of my other servers and the relay is working fine for forwarding alert emails from UPSes, Scanners, etc. It is only on the SQL server that I am running into problems.
I logged in as the sql domain account on the SQL server and created a new mail profile that uses SMTP to the relay and it sends fine from Outlook2003. I configured both SQLMail and SQL Agent to use the new profile. I rebooted the server,
logged in as the sql user again, started outlook, and then ran one of the jobs that sends an email as the last step. Job History says that all steps completed successfully. But the SMTP Relay doesn't even show an attempt to connect in the logs.
When i send a test message from the same MAPI profile using outlook the email goes through and shows in the logs. If i switch back to the exchange profile the emails get sent correctly and the jobs look the same in the history.
In my test system copy of these servers (backups restored to a isolated Hyper-V system) I uninstalled antivirus, made sure the firewall is turned off, and even tried uninstalling office 2003 and installing outlook 2000 (and that was hard to find a disk for...), creating a new profile, etc. But I just get the same behavior.
The fact i can send from the profile using Outlook means the profile and smtp relay are working fine. And SQL isn't giving any error messages...
Any suggestions besides keeping exchange up for anther 12 months? I've looked for xp_smtp_sendmail but sqldev.net website has gone away.
Thomas Price
IT Dept. TEAM