Email Client Threads

Message Threads

This tutorial is about manipulating message threads using Aspose.Email Cloud build-in client.

Using threads, you can easily structure emails in the mailbox. Instead of working with an unstructured list of messages, it is better to work and analyze only certain threads of emails. In the picture below you can see how the messages are arranged in threads:

todo:image_alt_text

Built-In Email Client

Aspose.Email Cloud API provides a built-in email client with a unified API, which supports different account types like SMTP, POP3, IMAP, EWS.

Threads support by protocols:

  • Exchange Web Services (EWS) Accounts: native support, no extra configuration needed. Exchange Web Services is an alternative to the MAPI protocol. EWS is used by the latest version of Microsoft Outlook for Mac and Microsoft Entourage for Mac.
  • POP3: thread support is implemented using message cache. Message cache location on storage should be specified. The Post Office Protocol allows manipulating the user’s client application with a mailbox supported on a mail server.
  • IMAP: thread support is implemented using message cache, at the moment. Native threads support will be implemented in a future version. The Internet Message Access Protocol is the Internet protocol that allows an email client to access emails on a remote mail server.
  • WebDav: threads are not supported.
  • Virtual Multi-account: gets threads from underlying accounts and provides them as is.

Thread Support using Message Cache

Aspose.Email Cloud built-in email client supports native threads for EWS accounts. For POP3 and IMAP accounts we provide this functionality using our own threads implementation. This implementation uses messages’ cache, located on Aspose Storage and our own threads algorithm, which generates threads based on message subject and participants.

Native threads for IMAP will be added in future versions. Message cache will still be used for IMAP accounts if the IMAP server does not provide native threads.

To support threads using cache, you should provide cache location during email account setup:

Setup account with cache file