Re: Application sending email



Here is some sources of information about Outlook/MAPI issues.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315886

Top Causes of SQL Server Downtime (Item #2)
http://www.sqlmag.com/Article/ArticleID/40011/sql_server_40011.html

http://www.karaszi.com/SQLServer/info_no_mapi.asp

Google for "SQL Server" + MAPI + problems

Microsoft has 'dumped' MAPI for SQL Server 2005, instead using a built in
SMTP client.

--> check out xp_smtpmail. It's very easy to set up and very easy to use.
<--

The question to raise, "Is it better to use a mail client that has no
documented problems running or SQL Server, or a mail client that has a long
history of problems, including causing the SQL Server to fail."

What difference to the developers as long as there is a flexible way to send
messages.

And your last question, how can you secure Outlook... possibly never.
Recognize that as the number one mail client, it is the biggest target for
any hackers (new expliots are regularly found), and what do hackers want to
hack? -data servers.

If you can't tell, I have a 'little' bias on this issue... Outlook/MAPI on
SQL Server is a big AND unnecesssary mistake.

--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."



"Cindy" <Cindy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:464BAE44-2A86-4DDA-AF3C-9726B9AFAC03@xxxxxxxxxxxxxxxx
Thanks for the information, but can you point me to some specifics about
the
Outlook security issues. I am bringing up new SQL database with
accounting
package. Package developers want to install Outlook on SQL server (has to
be
2000 not compatiable with 2005). Need facts to support my posiition. If
i
have no choice but to install outlook how can I secure?

If CDOSYS is klutzy is it more secure than outlook?

Thanks, Cindy

"Arnie Rowland" wrote:

Option 1 -very bad choice. Outlook has too many security issues to safely
install on a server.

Option 2. klutzy but will/could work But waitk there are better choices.

Option 3. SQL 2000 download xp_smtpmail from
http://www.sqldev.net/xp/xpsmtp.htm

Option 3. SQL 2005 -Use the included smtp mail server. Look up
sp_send_dbmail in Books on Line.
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."




"Cindy" <Cindy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:943EC1D1-1E2A-413A-8DF5-A5F919125DD9@xxxxxxxxxxxxxxxx
Hi:
I would like to know security implications on two different ways to
enable
an application to email alerts.

1. Installing outlook client for application to call.

2. Using CDOSYS to point to SMTP server and send email using AD
username/password.

Thanks for any input


.



Relevant Pages

  • Re: Integrating SQLServer and Exchange
    ... MAPI profile without actually needing a mail client of any sort. ... > This feature of SQL requires you install a mail client (ie outlook). ... >> When setting up SQL Server 2000 Standard or Enterprise, ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Mail
    ... SQL Server is running under. ... Installed Outlook 2000 and setup my profiles as Internet POP3. ... either there is no default mail client or the current mail client cannot ...
    (microsoft.public.sqlserver.tools)
  • PROBLEM WITH BCM AND SQL SERVER
    ... A problem with BCM started to occur on my computer recently. ... outlook I received an error message “BCM for Outlook could not connect to the ... When Trying To Start Sql server Through Computer Management I get ... about how to rebuild the master database, ...
    (microsoft.public.outlook)
  • Re: Outlook and SQL2000
    ... I've never tried it without Outlook. ... Mark Allison, SQL Server MVP ... Looking for a SQL Server replication book? ... Frequently Asked Questions - SQL Server - SQL Mail ...
    (microsoft.public.sqlserver.server)
  • SQL Mail: Missing From Address
    ... I have a Win2K server configured with SQL Server 2k. ... I have a single profile created with a single POP account. ... I sit at the console and start up Outlook. ... Is this an Outlook configuration ...
    (microsoft.public.outlook)