Exchange server 2013

Hi


Does Aspose support Exchange server version 2013? We have an exchange 2013 server and Aspose returns a System.InvalidOpertiaonException with message

"Instance validation error: ‘-1’ is not a valid value for Aspose.Email.Exchange.Schema.ExchangeVersionType"

We are using Aspose.Email version 3.2.1.0. It works fine for Exchange 2010.

Thanks.

Xu

Hi Xu,


Thanks for your inquiry.

At present, Aspose.Email for .NET doesn’t support Exchange server 2013. We are in process of implementing Exchange 2013 features via issue id: NETWORKNET-33413. I have also linked this thread with the logged ticket so that once the implementation completes, you’ll be notified here automatically.

Thanks for your reply. Is there a timeline for that?


Xu

One more question, do you support Exchange 2013 using IMAP? I guess no because we have trouble in accessing our Exchange 2013 using IMAP. Please confirm that. Thanks.


Xu

Hi Xu,


I have requested development team about an ETA of EWS support for Exchange Server 2013 and will update you here as soon as some feedback is available in this regard.

Regarding IMAP operations on Exchange 2013, could you please share a test account for us on your Exchange Server 2013, as it’ll need us some time to setup the environment which is currently unavailable? In any case, I can confirm this to you alongwith the feedback about the Exchange Server 2013 support.

Hi Xu,


With respect to your query about Exchange 2013 Support, I would like to share that we are planning to include this feature in our Aspose.Email for .NET 3.6.0 release which is due by the end of November, 2013. As soon as this feature is available, we’ll update you here with the release link.

I have discussed the issue of IMAP connectivity with Exchange 2013 with the development team and we are sure this should work with Exchange server 2013 as IMAP is a standard protocol and should not be affected. Please try it at your end again and let us know your feedback.

The issues you have found earlier (filed as NETWORKNET-33413) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
(1)