(SQL Server) Async Upload (Append) Email to an IMAP Mailbox

Use the AppendMailAsync method call to append an email to an IMAP mailbox.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @imap int
    -- Use "Chilkat_9_5_0.Imap" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Imap', @imap OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Connect to an IMAP server.
    -- Use TLS
    EXEC sp_OASetProperty @imap, 'Ssl', 1
    EXEC sp_OASetProperty @imap, 'Port', 993
    DECLARE @success int
    EXEC sp_OAMethod @imap, 'Connect', @success OUT, 'MY-IMAP-DOMAIN'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @imap, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @imap
        RETURN
      END

    -- Login
    EXEC sp_OAMethod @imap, 'Login', @success OUT, 'MY-IMAP-LOGIN', 'MY-IMAP-PASSWORD'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @imap, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @imap
        RETURN
      END

    -- Create a simple email with 2 recipients.
    DECLARE @email int
    -- Use "Chilkat_9_5_0.Email" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT

    EXEC sp_OASetProperty @email, 'From', 'support@chilkatsoft.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Chilkat Sales', 'sales@chilkatsoft.com'
    EXEC sp_OAMethod @email, 'AddTo', @success OUT, 'Chilkat GMail', 'chilkat.support@gmail.com'
    EXEC sp_OASetProperty @email, 'Body', 'This is a test email.'
    EXEC sp_OASetProperty @email, 'Subject', 'This is a test email.'

    -- Imagine we've sent this email via SMTP, and now we want to 
    -- save the email to our "Sent" mailbox.  On GMail, the mailbox name
    -- for sent email is "[Gmail]/Sent Mail".

    -- Call the async version of the AppendMail method to return a task object.
    DECLARE @task int
    EXEC sp_OAMethod @imap, 'AppendMailAsync', @task OUT, '[Gmail]/Sent Mail', @email
    EXEC sp_OAGetProperty @imap, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @imap, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @imap
        EXEC @hr = sp_OADestroy @email
        RETURN
      END

    -- Schedule the task for running on the thread pool.  This changes the task's state
    -- from Inert to Live.  The task is now running...
    EXEC sp_OAMethod @task, 'Run', @success OUT
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @task, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @task

        EXEC @hr = sp_OADestroy @imap
        EXEC @hr = sp_OADestroy @email
        RETURN
      END

    -- -------------------------------------------------------------------------------
    -- The following is a general note that applies to all programming languages:
    -- -------------------------------------------------------------------------------
    -- Your application can keep a reference to the task object and periodically check back later to see if it's finished.
    -- If your programming language is one that supports callbacks, then the TaskCompleted callback can
    -- be setup to be called when the task completes.  (See the "Async" category on example-code.com for more information.)
    -- 
    -- NOTE: This is very important:  A TaskCompleted callback runs in the background thread.  
    -- (All callbacks from an async task, such as AbortCheck, PercentDone, ProgressInfo, etc. are in the background thread.) 
    -- An application that uses TaskCompleted must be very careful.  
    -- For example, user interface elements (such as labels, text boxes, etc.) may not be directly
    -- accessible from a background thread, and could crash the application if directly accessed.  Also, attempting to debug
    -- code running in a background thread from an IDE, especially an older IDE (such as VB6) is likely to crash the IDE.

    EXEC @hr = sp_OADestroy @imap
    EXEC @hr = sp_OADestroy @email


END
GO