I setup SQL Server Notification Services (SSNS) at a client a few months back and there were the typical hangups that occur when implementing new technology and wondering... "does this really work?" Eight hours of reading and some manipulation of one of the sample applications and I had their new creating files. Of course it needed to send e-mails and another 4 hours later we got that fixed.
What were the those hangups? Well funny you should ask... I got to relive those issues the other night and afterwards thought, "hey I should blog this."
Well, with this SSNS application I got everything installed and working fine expect when ever I'd send out an e-mail I'd get the following error.
Description: The e-mail
address or SMTP server value is not valid.
EventParameters:
SMTP Server: 127.0.0.1
Message Recipients:
jason.strate@digineer.com
Description: The server
rejected one or more recipient addresses. The server response was: 550 5.7.1
Unable to relay for jason.strate@digineer.com
That's an interesting error. I verified the SMTP server... correct. E-mail addres... correct. I know, firewall... not that, I could ping the SMTP server from the SQL Server. Hey, I bet it's relay... nope that's setup.
At a loss for options I search google... nothing. MSDN forums... nothing.
Network Admin wonders... does the network card have two IPs? Why yes it does and the primary IP for the server was not the primary IP on the network card.
In the end the issue was in the network card configuration. The primary IP for the server needs to be the primary IP on the network card... Exchange is one of those funny applications that validates the IP of a relay request. Upside is that this is exactly as it should work... downside this was frustrating.
And now it is blogged and I'll never forget again.