ReleaseNotes.md
MAIL FROM or RCPT TO commands.("ALTERNATIVE")). (issue #1841)List<IMessageSummary> capacity estimation for Fetch (IList<UniqueId>, ...).(NIL NIL "" "localhost")
(issue #1471)ProtocolLogger (see the LogTimestamps and TimestampFormat
properties on ProtocolLogger).ProtocolLogger.RedactSecrets property to true. (issue #1174)RETURN () syntax
the same as RETURN (ALL). (issue #1177)MAIL FROM and RCPT TO commands even if a options.International is not
explicitly set to true if any of the mailbox addresses are international
addresses.
(issue #1026)-1 as a line count or octet count in the
BODYSTRUCTURE response.<CR><LF> in untagged FETCH responses.
(issue #954)Note: Developers using ImapFolder.GetStreamsAsync() will need to update their code as this release breaks API/ABI.
() as a message/rfc822 body token.
(issue #944)* BYE.
(issue #938)RET parameter value to the MAIL FROM command.API Changes Since 2.0.x:
body-fld-dsp token.MAIL FROM and RCPT TO commands. (issue #764)DATA command.SslProtocols property to IMailService (was already in MailService).* PREAUTH greeting when connecting to an IMAP server.var oauth2 = new SaslMechanismOAuth2 (username, auth_token);
client.Authenticate (oauth2);
Note: As of 2.0, XOAUTH2 is no longer in the list of SASL mechanisms that is tried when using the Authenticate() methods that have existed pre-MailKit 2.0. Instead, you must now use Authenticate(SaslMechanism, CancellationToken).
An example usage might look like this:
// Note: The Uri isn't used except with ICredentials.GetCredential (Uri) so unless
// you implemented your own ICredentials class, the Uri is a dummy argument.
var uri = new Uri ("imap://imap.gmail.com");
var oauth2 = new SaslMechanismOAuth2 (uri, username, auth_token);
client.Authenticate (oauth2);
* [COPYUID ...] response
without an OK (technically, the COPYUID resp-code should only appear in the tagged
response, but accept it anyway).* ID NIL response, return null for ImapClient.Identify().<CR><LF>
line endings.Note: If you are not yet ready to port your iOS application to the Unified API, you will need to stick with the 1.0.5 release. The Classic MonoTouch API is no longer supported.