Browse our Products

Aspose.Email for .NET 21.6 Release Notes

All Changes

EMAILNET-40263Email text missing contentBug
EMAILNET-40252AppointmentStateFlags missing when saving calendar to MSG fileBug
EMAILNET-40228Enumerating MAPI messages throws InvalidOperationExceptionBug
EMAILNET-40264Possible regression: mailMessage.GetHtmlBodyText(true) returns different contentBug
EMAILNET-40271Exception was thrown when getting multiple EWS clients at the same timeBug
EMAILNET-40269Connection with Exchange 2013 SP1 fails using EWSClientEnhancement
EMAILNET-40215ImapClient.SelectFolder method throws OperationCanceledExceptionEnhancement
EMAILNET-40244Add support for “Return request client ID” identifierFeature

New Enhancements

Using a return-client-request-id HTTP header in the EWSClient

The return-client-request-id header is sent in the request and used by the server to determine whether the client-request-id header specified by the client should be returned in the server response.

We have added the ReturnClientRequestId property to EWSClient:

// Gets or sets a value to indicate whether 
// the client requires the server-side to return the request-id.
public bool ReturnClientRequestId

Code sample:

using (IEWSClient client = TestUtil.CreateEWSClient(user))
    // Client will create random id and pass it to the server.
	// The server should include this id in request-id header of all responses.
    client.ReturnClientRequestId = true;
	client.LogFileName = "ews.log";

Setting the cryptographic protocol without compatibility checks

We have added an EmailClient.SetSupportedEncryptionUnsafe(EncryptionProtocols value) method. This method sets a certain cryptographic protocol without any compatibility checks.

For example:

TLS 1.2 is generally not supported by .NET Framework 3.5.

But when you call


TLS 1.2 will be used with .NET Framework 3.5.