SQL Server

SMTP using SOCKS5, SOCKS4 Proxy

Demonstrates how to communicate with an SMTP server via a SOCKS4 or SOCKS5 proxy. SQL Server

-- 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 use a SOCKS4 or SOCKS5 proxy, simply set the following
    -- properties prior to making any calls that communicate with
    -- an SMTP server:
    -- The SOCKS hostname may be a domain name or 
    -- IP address:
    EXEC sp_OASetProperty @mailman, 'SocksHostname', 'www.mysocksproxyserver.com'
    EXEC sp_OASetProperty @mailman, 'SocksPort', 1080
    EXEC sp_OASetProperty @mailman, 'SocksUsername', 'myProxyLogin'
    EXEC sp_OASetProperty @mailman, 'SocksPassword', 'myProxyPassword'
    -- Set the SOCKS version to 4 or 5 based on the version
    -- of the SOCKS proxy server:
    EXEC sp_OASetProperty @mailman, 'SocksVersion', 5
    -- Note: SOCKS4 servers only support usernames without passwords.
    -- SOCKS5 servers support full login/password authentication.

    -- 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 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