SQL Server

Send Signed Email using PFX File (long version)

Demonstrates how to send a signed email using a digital certificate w/ private key stored in a PFX file. 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

    -- Set the SMTP server.
    EXEC sp_OASetProperty @mailman, 'SmtpHost', 'smtp.mymailserver.com'

    -- Create a new email object
    DECLARE @email int
    EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT

    EXEC sp_OASetProperty @email, 'Subject', 'This email is signed'
    EXEC sp_OASetProperty @email, 'Body', 'This is a digitally signed mail'
    EXEC sp_OASetProperty @email, 'From', 'Chilkat Admin <admin@chilkatsoft.com>'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Chilkat Support', 'support@chilkatsoft.com'

    -- Indicate that the email should be sent signed.
    EXEC sp_OASetProperty @email, 'SendSigned', 1

    -- Load a PFX file into a certificate store object.
    -- Then locate the certificate matching the  sender's email address,
    -- and use it for signing.
    -- (a PFX file may contain more than one certificate.)
    DECLARE @certStore int
    EXEC @hr = sp_OACreate 'Chilkat.CertStore', @certStore OUT

    -- The 1st argument is the path of the PFX file, the 2nd arg is the 
    -- PFX file's password:
    EXEC sp_OAMethod @certStore, 'LoadPfxFile', @success OUT, '/pfx_files/chilkatsoft_secret.pfx', 'secret'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @mailman
        EXEC @hr = sp_OADestroy @email
        EXEC @hr = sp_OADestroy @certStore
        RETURN
      END

    -- Find the certificate for the email address:
    DECLARE @jsonE int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonE OUT

    EXEC sp_OAMethod @jsonE, 'UpdateString', @success OUT, 'email', 'admin@chilkatsoft.com'

    DECLARE @cert int
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT

    EXEC sp_OAMethod @certStore, 'FindCert', @success OUT, @jsonE, @cert
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @mailman
        EXEC @hr = sp_OADestroy @email
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonE
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    -- Alternatively, if a PFX file is known to contain a single certificate,
    -- you may load it directly into a Chilkat certificate object.
    -- This snippet of source code shows how:
    DECLARE @cert2 int
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert2 OUT

    -- The 1st argument is the filename, the 2nd arg is the 
    -- PFX file's password:
    EXEC sp_OAMethod @cert2, 'LoadPfxFile', @success OUT, '/pfx_files/chilkatsoft_secret.pfx', 'secret'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @cert2, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @mailman
        EXEC @hr = sp_OADestroy @email
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonE
        EXEC @hr = sp_OADestroy @cert
        EXEC @hr = sp_OADestroy @cert2
        RETURN
      END

    -- This example will use the cert from the certStore...
    EXEC sp_OAMethod @email, 'SetSigningCert', @success OUT, @cert

    -- Signed email can be sent in two different ways.  
    -- In a multipart/signed email, the signature is attached as a separate MIME part.
    -- In an opaque email (signedData) the content of the email is encapsulated within the signature
    -- and the email is sent as "application/pkcs7-mime". 
    -- Either should be fine, but some receiving systems might require one or the other..
    EXEC sp_OASetProperty @mailman, 'OpaqueSigning', 0

    -- Send a signed email.
    EXEC sp_OAMethod @mailman, 'SendEmail', @success OUT, @email
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
      END
    ELSE
      BEGIN
        -- The LastErrorText property provides information
        -- even when successful.
        EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0

        PRINT 'Mail Sent!'
      END

    EXEC @hr = sp_OADestroy @mailman
    EXEC @hr = sp_OADestroy @email
    EXEC @hr = sp_OADestroy @certStore
    EXEC @hr = sp_OADestroy @jsonE
    EXEC @hr = sp_OADestroy @cert
    EXEC @hr = sp_OADestroy @cert2


END
GO