Hi All,
I am a little wary of posting in this estemed company, as I'm a SQL pro, not a .NET expert, but I have a problem sending mail from SQL Server 2005 Database mail, and searching through the forums, the only place where I have seen a similar issue is in this forum:
(http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=112971&SiteID=1).
When I try to send mail I get an error in the event log:
"The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 2 (2006-02-20T10:55:30). Exception Message: Cannot send mails to mail server. (Command not implemented. The server response was: Command not Supported)."
This seems to imply a server issue, and the above post suggests I look at the NetMon trace to see what is happening. I can look at Net Mon, but it does not make a lot of sense to me - other than I can see which packets went between my server and the Exchange server.
Can anyone please help What is the best way to post .cap files if necessary
Thanks in advance,
Richard R.
SQL 2005 SMTP Client problem
mbutcher
Send the .cap files to
me dgorti_____don't spam ___ @ microsoft . com ___
Typically this means that the server sent a command that teh client did not understand.
or vice versa. We can take a look at these in the capture file
john mc
Hi,
It will be en route just as soon as the VPN decides to let me re-connect from home :-( Failing that, first thing tomorrow UK time.
Many thanks,
Richard
Viral
Hi Durgaprasad,
Have you been able to look at the .cap file at all
I sent it some time back, hopefully to the correct e-mail address. Can you let me know if you will be able to look at them or not, as we are getting up to project completion, and are still stumped for an answer.
Thanks for any help you can offer,
Best Regards,
Richard
Noah Nadeau
Just to close out this thread, should anyone be reading it in the future:
It appears that the exchange server is set up using non-standard ports to receive on, and also McAfee security is running to block data on all but the narrowly specified ports. Our exchange people kindly ommitted to tell us this, but the upshot is that nothing can send mail out through the Exchange server. The error message is a bit confusing, but the root cause is security, not SQL or the client.
Regards,
Rich