April 4, 2007 at 5:33 am
I am in the process of learning about SQL Mail, is it possible to send an email from my local email account on the network via SQL at the end of an SP and not have to wait for our security person to give me the third degree as to why I need a seperate email account for SQL Mail?
April 4, 2007 at 7:17 am
You can possibly do this with xp_sendmail and authenticate to an SMTP mail server.
The other thing to explain to your network person is that you need alerts sent to you by SQL Server and SQLMail requires its own email account.
April 5, 2007 at 3:16 am
If you run SQL Server using a domain service account, try asking for mail capability to be added to that account. As everything is not totally new, this may be easier to get through your approvals process.
It may seem odd, but most people are just trying to do their job. If you present a business case why a mail account is needed, then it is harder for this to be refused.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 5, 2007 at 8:53 am
I don't know if this would work or not, since I've not had the chance or available equipment to test it. It looks to me like SQL Mail just uses MAPI to deliver messages. I've had pretty good results using Thunderbird on a regular desktop as the MAPI service, and I've been wondering whether it would work to install Thunderbird on the database server and configure it to use a regular SMTP account rather than asking for a new GroupWise account just for SQL Mail. (I guess technically Outlook can do the same, but it's a no-no on our network.)
--Andrew
April 5, 2007 at 4:51 pm
From BOL:
The computer running SQL Server must be set up as an e-mail client. SQL Server Enterprise Manager is used to assign an e-mail account and password to the SQL Server installation.
So you need something like Outlook on your database server as well as a valid mail account on your mail/Exchange server. I've only used it in conjunction with Exchange. I believe there is a way to set up a domain logon such that you can't sit at a PC on your network and actually logon to Windows. That way, the server monkeys can set up the logon, tell Exchange about it somehow, and it's not a security risk to network resources. The benefit to you of using a domain logon is that the "real" (hand-crafted?) emails you send don't get confused with the robot emails that SQL mail sends.
Somewhat alternatively, you can use xp_smtpmail, which is a freeware product that doesn't require Outlook or other email client on your database server (which I've always thought of as hokey). But if you have a network security cop, he will have a seizure if you tell him you want to install freeware on your server.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply