MailBee.NET Objects v12.0

Adds compatibility for Microsoft Visual Studio 2019 and improves support for .NET Core 2.1 and 2.2.
July 23, 2019 - 14:10
New Version

Features

  • .NET Core 2.0 / .NET Standard 2.0 edition revised and improved, including better support of .NET Core 2.1 and 2.2.
  • .NET Standard 2.0 support in UWP. UWP apps targeting Windows 10 Fall Creators Update and newer can use the fully-functional .NET Standard 2.0 edition of MailBee.NET Objects. Special UWP edition of MailBee.NET Objects which can work with older UWP platform is still there as well.
  • .NET Core 2.0 sample projects and tutorials added (UWP, console and ASP.NET Core). They feature OAuth 2.0 authentication against Google (Gmail.com) and Microsoft (Live.com, Outlook.com, Hotmail.com) providers along with sending and receiving e-mail using these providers.
  • Improved support of Outlook Converter functionality on iOS and Android.
  • EWS is now supported for .NET Core (.NET Core 2.0+ required). However, only async methods are supported (in .NET Framework edition it's quite opposite, only sync method are supported - this is the limitation of the Managed EWS API).
  • EWS and PDF functionality was moved into friend assemblies. Because EWS and PDF are dependent on other libraries, this caused these libraries be included in the project even if they are not actually needed. Now if the app does not use PDF or EWS, the corresponding libraries will never be referenced, neither directly nor indirectly. Separate Nuget packages for MailBee.NET.EWS and MailBee.NET.PDF were added as well.
  • Exception messages now suggest setting SslProtocol to TlsAuto in case if SSL/TLS handshake fails due to unsupported protocol (usually TLS 1.0 in case if the server requires TLS 1.2).
  • More accurate handling of SSL/TLS related exceptions (now throws MailBeeException instead of system-level AuthenticationException).
  • TLS 1.2 is now fully supported in .NET 2.0/3.5 (despite the fact that .NET 2.0/3.5 itself does not support anything better than TLS 1.0).
  • Documentation now highlights that you must install System.Text.Encoding.CodePages NuGet package for .NET Core 2.0+ apps.
  • Added 'ConfigureAwait(false)' in all internal async calls.
  • Memory/performance optimizations on reading .EML data from stream.
  • 'MailMessage.GetHtmlAndSaveRelatedFiles' and other similar methods now support 'cid:filename'-like CIDs.
  • 'MsgConvert.PreferAddressesFromInternetHeaders' property lets you control from which parts of .MSG file to extract the headers (as sometimes the .MSG file can have these values available in multiple locations and these values are not the same).
  • 'MailMessage.SetDomainKeysSignOnSend' property enables automatic DKIM signing when sending the message.
  • Empty headers are now added to the message being sent in case if they are DKIM signed.
  • S/MIME signatures are now time-stamped by default. 'Smime.TimestampOnSign' property lets you turn this off (as it's a time-consuming network operation).
  • S/MIME signatures now include full certificate chain, can be turned off with 'Smime.IncludeWholeChainOnSign' property.
  • 'Envelope.HasSystemFlag', a helper method to check the envelope for particular IMAP flags.
  • OAuth 2.0 is now supported in EWS, see Ews.SetCredentials(ExchangeCredentials) method.
  • Bounce database updated.
  • Misc. bugfixes to the code and documentation.
  • Also tested with Visual Studio 2019.
MailBee.NET Objects

MailBee.NET Objects

Bring e-mail support to your .NET applications in a few lines of code.

Got a Question?

Live Chat with our Afterlogic licensing specialists now.