Delete Messages from PST File Permanently & Enhanced EML to MSG Conversion inside .NET Apps

Aspose team is pleased to announce the release of Aspose.Email for .NET 17.4.0. This month’s release comes with several enhancements related to Outlook messages and Storage files i.e. PST/OST. Aspose team has also fixed a number of bugs that further improves the overall functionality and stability of the API in terms of expected output. Consider a scenario where users are given a PST file and a set of messages that have been designated as attorney-client privileged. Given a list of entry IDs for those privileged messages, users are supposed to remove those messages and forward the PST to opposing legal counsel. If the deleted messages are recoverable by forensic tools, this defeats the purpose. To help users about this, Aspose team is glad to share that this month’s release enhances the functionality of deleting messages from a PST file permanently. This means these are no more recoverable from the PST file with recovery tools. There is no public API change that users need to incorporate in their code to achieve this. Users existing code sample for deleting messages from PST file will do the job with this latest release of the API. This month’s release also provides support for a new Mapi property i.e. PT_FLOAT. The API already supports other properties as well and the addition of this new one further enhances the list of such propertie. Following code sample shows how to add such type of MAPI property to an Outlook message. In addition to the enhancements mentioned above, this month’s release also includes several bug fixes for the issues reported by API users. Details about these can be found in release notes section of our documentation. The main bug fixes & improved features added in this release are listed below

• Delete messages from PST permanently
• Option to add PT_FLOAT property
• TNEF issue resulting in NDR on Exchange Server
• Performance issue while adding MapiMessage to PST
• EML to MHTML converts German characters to Garbage values
• Attachment data is set as message body instead
• Accepted appointment cannot be saved in PST
• Provide Logging facility on session based for all communication clients
• PNG images corrupted after using them as mail attachments
• Saving EML to MSG causes inline images appear as attacments
• Attachment NamedProperties lost while fetching message from PST
• MailMerge not working for TO, CC and BCC
• MapiProperties lost after adding message to PST
• Information not read from VCF file
• Body could not be read from MSG file
• EML to MSG convertion Issue with embedded Signed and Encrypted message
• IGmailClient.UpdateContact raises Aspose.Email.GoogleClientException
• IGmailClient.ListAppointments raises Aspose.Email.GoogleClientException
• IGmailClient.GetSettings raises Aspose.Email.GoogleClientException
• Exception is raised while converting EMLs to tiff
• Saving MSGs/Calendar Items from PST raises exception
• MailPrinter raises exception converting email to TIFF

Other most recent bug fixes are also included in this release.

Comments

  • Aspose is proud to expand its APIs family with the addition of a new product known as Aspose.Email for Python via .NET. The addition of this new API extends the Aspose.Email Product family to several other platforms. The API lets Application developers to embed email related functionality in their Python applications without worrying about the underlying details of message formats. It is easy to use, rich with emailing functionality and provides the ease of development in native 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, Installating Aspose.Email for Python via .NET, lists the detailed steps for installing the API from both these sources. The API functionality comprises of rich set of emailing features that continue to be part of our other APIs. It not only supports variety of email message formats, but also supports popular mail storage file types. In addition, it provides support for well-known emailing protocols. The main features added in this release are listed below

    • 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 with 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

  • Aspose team is pleased to announce the new release of Aspose.Email for Android via Java 18.11. This release includes few enhancements in API and overall functionality of the API has been improved as a result of several bug fixes. This release includes few enhancements to the API’s functionality. These enhancements include modification of product id, new properties are introduced to specify Created Date and Last Modified Date for ICS. This release also enhances the functionality for working with digitally signed emails. This release includes several improvements in term of bug fixes, such as Working with MapiMessage.SetBodyContent(), Recognition of unreadable characters, Reading of SOAP header Action, IMAP backup to PST, Working with GoogleClient, Working with FolderInfo.deleteChildItem method, PST Modification, Working with EML and conversion of MSG to HTML, Exporting calendar from PST file to Exchange calendar, Copying messages from one PST to another, Extracting MSG from PST file, Email To PDF Conversion, Clearing Attachments from TNEF, Working with VCF Contact and Conversion from VCF to MSG, Converting ICS to MSG, Converting EML messages into MapiMessage, Working with ForwardMessageBuilder and Formatting while Converting to MHTML and HTML. The main features added in this release are listed below

    • Specify created and last modified dates in ICS
    • Modification of PRODID in ICS
    • Attachments are missing in the signed email
    • Fail to save attachments for Digitally Signed emails
    • MapiMessage.SetBodyContent() generates exception if string ends with opening angle bracket
    • Aspose.Email and Outlook display different text in case of unreadable characters.
    • The output MSG got truncated
    • FolderInfo.deleteChildItem method call thrown NullPointerException
    • PST modification. System.ArgumentException: An item with the same key has already been added
    • Unable to read To Email Address from EML file
    • Converting MSG to HTML results in missing closing span tag
    • An error raises while coping a calendar from PST file to Exchange calendar
    • Copying messages from one PST to another leads to losing attachments of enclosed messages
    • Extracted MSG from PST file has corrupted attachment
    • Incomplete MHT file when saving a Calendar Event
    • Email To PDF conversion adds styles to the top of the document
    • Calendar is added as attachment file in the EML message instead of preview
    • Number is Skipped in HTML Body Content
    • Japanese Characters Appearing as Question Marks in Preview
    • How to get date in local format in MHT from outlook event
    • Clearing Attachments from TNEF is not working
    • MailMessage.ValidateMessage fails for certain text files
    • FileUnder property is not set when VCF contact is loaded to MapiContact
    • Display as shows only email address after converting from VCF to MSG
    • Comma(,) added to address fields when converting from VCF to MSG
    • Converting ICS to MSG
    • Mail body does not contain URLs
    • ICS generated by Aspose.Email does not wrap lines according to specification
    • PRODID has a typo error in ICS file
    • The space character separator is missing after extracting from PST
    • Getting NulReferenceException while converting EML messages into MapiMessage
    • ForwardMessageBuilder adds only display name in message body
    • Format-Issue in Converting to MHTML and HTML
    • Failed to Set License

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

In this Discussion