We are pleased to announce the launch of Aspose.Email for Python via .NET. The addition of this new API extends the Aspose.Email Product family to embed email related functionality in Python applications. Aspose.Email for Python lets you create, manipulate or convert popular email formats including MSG, EML, EMLX & MHT using Python. It is easy to use, rich with emailing functionality and provides the ease of development in native python.

Email API for Python - Create, Manipulate and Send Emails in Python

Aspose.Email for Python via .NET is available at PyPI (Python Package Index) repository as well as in Aspose downloads section. The API documentation section, Installation of Aspose.Email for Python via .NET, lists the detailed steps for installing the API from both of these sources.

Python Email API - Features Overview

The API comprises of the rich set of emailing features that continue to be part of our APIs. It not only supports a variety of email message formats but also supports popular mail storage file types. In addition, it provides support for well-known emailing protocols. Following is a list of features supported by the API:

  • Working with Mime messages
  • Working with Email attachments
  • Conversion of messages from one format to another
  • Working with Outlook Message formats
  • Support for Outlook Storage Files including OST and PST
  • Work with Appointments
  • Create and send emails using SMTP protocol
  • Working wit POP3 and IMAP protocols for retrieving messages from server
  • Support for filtering messages from email servers using POP3 and IMAP
  • Create and send appointments using SMTP
  • Working with Thunderbird storage files
  • Working with Outlook Calendar, Contacts, Tasks and Notes
  • Creating Voting options and Follow Up flags

Details about the supported features can be found in the Features Overview section of API documentation.

API Limitations

The first release of Aspose.Email for Python via .NET includes certain limitations as well compared to the .NET equivalent of the API. These are:

  • You cannot embed linked images into message body in both RTF as well as HTML format
  • It also has no functionality of Signing or Encrypting/Decrypting messages
  • Support for Exchange Server clients is not available
  • Support for additional MAPI Properties is not available

We plan to implement these features in future versions of the API.

API Resources