MailKit 2.3.0

Learn more about Target Frameworks and .NET Standard.

• .NETFramework 4.5

  • MimeKit (>= 2.3.0)

• .NETStandard 1.3

  • MimeKit (>= 2.3.0)
  • System.Net.NameResolution (>= 4.3.0)
  • System.Net.Security (>= 4.3.2)
  • System.Runtime.Serialization.Primitives (>= 4.3.0)

• .NETStandard 1.6

  • MimeKit (>= 2.3.0)
  • System.Net.NameResolution (>= 4.3.0)
  • System.Net.Security (>= 4.3.2)
  • System.Runtime.Serialization.Primitives (>= 4.3.0)

• .NETStandard 2.0

  • MimeKit (>= 2.3.0)
  • System.Net.NameResolution (>= 4.3.0)
  • System.Net.Security (>= 4.3.2)
  • System.Runtime.Serialization.Primitives (>= 4.3.0)

• MonoAndroid 0.0

  • MimeKit (>= 2.3.0)

• Portable Class Library (Windows 8.1, WindowsPhoneApp 8.1)

  • MimeKit (>= 2.3.0)

• Xamarin.iOS 0.0

  • MimeKit (>= 2.3.0)

* Improved the default SSL/TLS certificate validation logic.
* Improved exception messages for the POP3 LIST and STAT commands.
* Modified Pop3Client to accept negative values for the 'octets' value in the STAT response. (issue #872)
* Added work-around for IMAP BODYSTRUCTURE responses that treat multiparts as basic parts. (issue #878)
* Added check to make sure that MD5 is supported by the runtime and automatically disable support for CRAM-MD5 and DIGEST-MD5 SASL mechanisms when MD5 is not supported.
* Added a Stream property to ProtocolLogger.
* Fixed fetching of PreviewText items if the body's ContentTransferEncoding is NIL. (issue #881)
* Improved processing of pipelined SMTP commands to provide better exception messages. (issue #883)
* Modified SmtpClient.Send() and SendAsync() methods to not call MimeMessage.Prepare() if any DKIM or ARC headers are present in order to avoid the potential risk of altering the message and breaking the signatures within those headers.
* Added protected SmtpClient.SendCommand() and SendCommandAsync() methods to allow custom subclasses the ability to send custom commands to the SMTP server. (issue #891)
* Allow SmtpClient subclasses to override message preparation by overriding a new SmtpClient.Prepare() method. (issue #891)
* Improved ImapFolder's ModSeqChanged event to set the UniqueId property if available in unsolicited FETCH notifications including a MODSEQ and UID value.
* Fixed the IMAP client logic to properly handle lower or mixed case IMAP tokens. (issue #893)
* Added support for IMAP's ANNOTATE-EXPERIMENT-1 extension. (issue #818)
* Always use the SMTP BDAT command instead of DATA if CHUNKING is supported. (issue #896)
* Improved SmtpClient to include a SIZE= parameter in the MAIL FROM command if the SIZE extension is supported. Progress reporting will now always have the expected message size available as well.

API Changes Since 2.0.x:

* Obsoleted SearchQuery.HasCustomFlags() and SearchQuery.DoesNotHaveCustomFlags(). These are now SearchQuery.HasKeywords() and SearchQuery.NotKeywords(), respectively.
* Obsoleted SearchQuery.DoesNotHaveFlags() in favor of SearchQuery.NotFlags().
* Obsoleted the IMessageSummary.UserFlags property in favor of IMessageSummary.Keywords.
* Obsoleted the MessageFlagsChangedEventArgs.UserFlags property in favor of MessageFlagsChangedEventArgs.Keywords.
* All IMailFolder.Fetch and IMailFolder.FetchAsync methods that took a HashSet<string> userFlags argument now take an IEnumerable<string> keywords argument. Note: this only affects you if your code used named method parameters (e.g. userFlags: myUserFlags).

Note to users upgrading from MailKit 1.x:

In order to authenticate using the XOAUTH2 SASL mechanism, you must now use the following approach:

client.Authenticate (new SaslMechanismOAuth2 (username, auth_token));