Xbase++

Async Upload (Append) Email to an IMAP Mailbox

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

LOCAL nSuccess
LOCAL oImap
LOCAL oEmail
LOCAL oTask

nSuccess := 0

//  This example assumes the Chilkat API to have been previously unlocked.
//  See Global Unlock Sample for sample code.

oImap := CreateObject("Chilkat.Imap")

//  Connect to an IMAP server.
//  Use TLS
oImap:Ssl := 1
oImap:Port := 993
nSuccess := oImap:Connect("MY-IMAP-DOMAIN")
IF (nSuccess != 1)
    ? oImap:LastErrorText
    oImap:destroy()
    RETURN
ENDIF

//  Login
nSuccess := oImap:Login("MY-IMAP-LOGIN", "MY-IMAP-PASSWORD")
IF (nSuccess != 1)
    ? oImap:LastErrorText
    oImap:destroy()
    RETURN
ENDIF

//  Create a simple email with 2 recipients.
oEmail := CreateObject("Chilkat.Email")
oEmail:From := "support@chilkatsoft.com"
oEmail:AddTo("Chilkat Sales", "sales@chilkatsoft.com")
oEmail:AddTo("Chilkat GMail", "chilkat.support@gmail.com")
oEmail:Body := "This is a test email."
oEmail: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.
oTask := oImap:AppendMailAsync("[Gmail]/Sent Mail", oEmail)
IF (oImap:LastMethodSuccess != 1)
    ? oImap:LastErrorText
    oImap:destroy()
    oEmail:destroy()
    RETURN
ENDIF

//  Schedule the task for running on the thread pool.  This changes the task's state
//  from Inert to Live.  The task is now running...
nSuccess := oTask:Run()
IF (nSuccess != 1)
    ? oTask:LastErrorText
    oTask:destroy()
    oImap:destroy()
    oEmail:destroy()
    RETURN
ENDIF

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

oImap:destroy()
oEmail:destroy()