Dotnet
Aspose.Email for .NET v24.9.0
Aspose.Email for .NET is a comprehensive set of Email Processing APIs that can be used to build cross-platform applications with the ability to create mails, manipulate, analyze, convert and transmit messages without using Microsoft Outlook or Office Automation....
Description
Aspose.Email for .NET is a comprehensive set of Email Processing APIs that can be used to build cross-platform applications with the ability to create mails, manipulate, analyze, convert and transmit messages without using Microsoft Outlook or Office Automation. The API provides the email manipulation features such as addition, extraction or removal of attachments from a message object, customization of message headers by adding or removing recipients or changing the subject and more. The overview of these features and their use with code samples you can find in our documentation.
Aspose.Email for .NET makes it easier for the developers to work with Microsoft Outlook & Mozilla Thunderbird as it supports a number of formats such as MSG, EML, EMLX, PST, OST, MBOX and MHT. The full number of formats you can find on the list of the supported file formats.
Aspose.Email for .NET also provides the ability to manage message storage files such as Personal Storage Files (PST) & Offline Storage Files (OST) & MBOX. Developers can use the API to send & receive emails via a number of popular protocols like POP3, IMAP & SMTP or connect with Microsoft Exchange Server via Exchange Web Services and Microsoft Graph to send & receive emails with attachments and list or remove messages from the server.
Dynamically Convert Messages to Multiple Email Formats in .NET
Aspose.Email is a good choice if you are looking for an API to convert emails to various file formats. For example, you can easily convert MSG files to EML, HTML or MHTML formats or vice versa. API has exposed interfaces for all of the possible conversion processes while hiding the underlying format specifications thus making it easy for the developers to integrate the API in their applications. Any of the supported conversion processes are as simple as loading the source file in the library object model and calling the Save method with appropriate parameters.