Visual FoxPro

Async Upload (Append) Email to an IMAP Mailbox

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

LOCAL lnSuccess
LOCAL loImap
LOCAL loEmail
LOCAL loTask

lnSuccess = 0

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

loImap = CreateObject('Chilkat.Imap')

* Connect to an IMAP server.
* Use TLS
loImap.Ssl = 1
loImap.Port = 993
lnSuccess = loImap.Connect("MY-IMAP-DOMAIN")
IF (lnSuccess <> 1) THEN
    ? loImap.LastErrorText
    RELEASE loImap
    CANCEL
ENDIF

* Login
lnSuccess = loImap.Login("MY-IMAP-LOGIN","MY-IMAP-PASSWORD")
IF (lnSuccess <> 1) THEN
    ? loImap.LastErrorText
    RELEASE loImap
    CANCEL
ENDIF

* Create a simple email with 2 recipients.
loEmail = CreateObject('Chilkat.Email')
loEmail.From = "support@chilkatsoft.com"
loEmail.AddTo("Chilkat Sales","sales@chilkatsoft.com")
loEmail.AddTo("Chilkat GMail","chilkat.support@gmail.com")
loEmail.Body = "This is a test email."
loEmail.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.
loTask = loImap.AppendMailAsync("[Gmail]/Sent Mail",loEmail)
IF (loImap.LastMethodSuccess <> 1) THEN
    ? loImap.LastErrorText
    RELEASE loImap
    RELEASE loEmail
    CANCEL
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...
lnSuccess = loTask.Run()
IF (lnSuccess <> 1) THEN
    ? loTask.LastErrorText
    RELEASE loTask
    RELEASE loImap
    RELEASE loEmail
    CANCEL
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.

RELEASE loImap
RELEASE loEmail