Search Messages With Paging Support Using IMAP & Sending Calendar Invitation Using .NET

It included support for sending calendar invitations using its Exchange Web Service (EWS) client and introduces a new feature where the ImapClient API has been enhanced for moving a message from one folder to another. It enhanced the API's IMAP client for searching messages with paging support simultaneously and saving messages as Microsoft Office Template (OFT) file. It improved Independent implementation of Paging Support in Email Clients and Setting TimeZone Support for EWS Client.

Press Release-
Apr 28, 2016

Lane Cove, NSW,
April 28, 2016 (Newswire.com) -
This article explains the new and enhanced features included Aspose.Email for .NET 6.4.0. Aspose.Email API now lets users send calendar invitations using its Exchange Web Service (EWS) client. This requires, however, to delegate user rights to the receiver who the calendar invitation is sent. The invitation must be sent by converting from MSG format to TNEF EML format using the IEWSClient of the API as illustrated in thhe documentation article, sending calendar invitation. This month’s release introduces a new feature where the ImapClient API has been enhanced for moving a message from one folder to another. The MoveMessage method of ImapClient API provides this functionality using the message’s unique id or sequence nmber. It has also enhanced the API’s IMAP client for searching messages with paging support simultaneously. The API now provides the ListMessagesByPage method that takes ImapQueryBuilder and number of items per page as input parameters. This allows to list filtered messages from the server with control on the number of items to be retrieved per page. This month’s release introduces another enhancement of saving messages as Microsoft Office Template (OFT) file. The MailMessage as well as MapiMessage API can be used to save the messages as OFT file format. We introduced features of paging support for listing messages, appointments and folders in IMAP as well as Exchange clients in one of Aspose previous releases. The implementation, though providing the functionality, was not that much user friendly. It now enhances this functionality by implementing it in separate classes. The new implementation provides ease of use and better understanding of the functionality. Aspose.Email API now provides support for setting Timezone context for EWS Client. This release also enhances the functionality of creating a task. The API now supports creating an Outlook task with zero occurrences similar to Microsoft Outlook. This can be achieved by using the StartDate and EndDate properties of MapiCalendarRecurrencePattern. This month’s release also fixes a number of bugs reported with the earlier versions of the API. The product release notes of this month’s version lists all of these along with the status. The main bug fixes & improved features added in this release are listed below

• Support for saving MailMessage and MapiMessage to OFT format• Sending Calendar Invitation Email• Issue while having hyphen in domain name• Leaving out Attachment Name while saving using Aspose.Email?• IMAP: Combination of MailQuery and Paging Support• Support of context timezone for EWS client• ImapClient: Provide option to Move Message• Move paging parameters to separate class• Provision of Getting MBox Marker• Attachments repeated wrongly in the MailMessage.Attachments collection while loading the EML• Splitting PST does not split items at root folder• Journal item raise error when opened in PST• Task with 0 occurrences takes long time to save as MSG file• Messages could not be read from MBOX• Messages extracted from PST doesn't have Body information• MapiNote re-saved using Aspose.Email API doesn't open in Outlook• Msg to MHTML: Inline image missing in output• MSG to MSG/HTML: Table borders and cells are missing in output• Unable to set ReplyTo with uppercase letters• EML to MSG: Message body is missing• MSG to EML: API Halts while extracting calendar items from PST file• EML->EML: Subject is lost• Problem with Signed messages in presence of attachment• Assigning weekly MapiCalendar recurrence to MapiTask hangs• MailMessage.Save raises OutOfMemoryException for this HTML file• Pop3Client.ListMessages raises exception with latest API• Exception raised when Task with MapiCalendarWeeklyRecurrencePattern contains 0 occurrence• MailboxConverter.ConvertPersonalStorageToMbox raises System.UnauthorizedAccessException• EML to MSG raises Exception• Daily, weekly and yearly recurrence pattern raise exception while adding to PST• Detach Add Signature option raises exception with attachment

It allows saving 3D model in the Universal 3D file format, including meshes, materials, hierarchy, lights, cameras, animation and skeletons (bones), etc. This version gives protection to the vertex element data during the conversion of a 3D scene mesh to the triangle mesh. It also enhanced the reading support of Universal 3D files.

It improved memory consumption while rendering a report to presentation. This optimal memory consumption ensures there are no OutOfMemory Exceptions during rendering operation. It also enhanced support for image rendering and fixed problem of text overflowing. Moreover, it has resolved issues related to height of table rows and width of table columns, which results in improved rendering of the data in a table.

It includes a new feature of detecting file format of provided email message file. It also introduced a feature for exporting message data to html format in one of the earlier releases. This month's release further enhances this feature by providing the capability of writing message headers to html output. Moreover, it also provides the capability to sign messages with the option to detach signature before sending. This month release also fixes a number of bugs that were reported by customers.