SQL Server
SQL Server
SMTP using HTTP Proxy
Demonstrates how to communicate with an SMTP server via an HTTP proxy.Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
-- Important: Do not use nvarchar(max). See the warning about using nvarchar(max).
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
-- The mailman object is used for sending and receiving email.
DECLARE @mailman int
EXEC @hr = sp_OACreate 'Chilkat.MailMan', @mailman OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- To connect through an HTTP proxy, set the HttpProxyHostname
-- and HttpProxyPort properties to the hostname (or IP address)
-- and port of the HTTP proxy. Typical port numbers used by
-- HTTP proxy servers are 3128 and 8080.
EXEC sp_OASetProperty @mailman, 'HttpProxyHostname', 'www.my-http-proxy.com'
EXEC sp_OASetProperty @mailman, 'HttpProxyPort', 3128
-- Important: Your HTTP proxy server must allow non-HTTP
-- traffic to pass. Otherwise this does not work.
-- Set the SMTP server.
EXEC sp_OASetProperty @mailman, 'SmtpHost', 'smtp.chilkatsoft.com'
-- Set the SMTP login/password (if required)
EXEC sp_OASetProperty @mailman, 'SmtpUsername', 'myUsername'
EXEC sp_OASetProperty @mailman, 'SmtpPassword', 'myPassword'
-- Create a new email object
DECLARE @email int
EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT
EXEC sp_OASetProperty @email, 'Subject', 'This is a test'
EXEC sp_OASetProperty @email, 'Body', 'This is a test'
EXEC sp_OASetProperty @email, 'From', 'Chilkat Support <support@chilkatsoft.com>'
EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Chilkat Admin', 'admin@chilkatsoft.com'
-- Call SendEmail to connect to the SMTP server via the HTTP proxy and send.
-- The connection (i.e. session) to the SMTP server remains
-- open so that subsequent SendEmail calls may use the
-- same connection.
EXEC sp_OAMethod @mailman, 'SendEmail', @success OUT, @email
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
RETURN
END
-- Some SMTP servers do not actually send the email until
-- the connection is closed. In these cases, it is necessary to
-- call CloseSmtpConnection for the mail to be sent.
-- Most SMTP servers send the email immediately, and it is
-- not required to close the connection. We'll close it here
-- for the example:
EXEC sp_OAMethod @mailman, 'CloseSmtpConnection', @success OUT
IF @success <> 1
BEGIN
PRINT 'Connection to SMTP server not closed cleanly.'
END
PRINT 'Mail Sent!'
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @email
END
GO