Jeffrey Stedfast

@peterdettman I'll try to look into the test failures this weekend. Is the published fix on nuget.org?

Hmmm, odd, I installed the 2.4.0-beta.61 version and MimeKit UnitTests all passed?

Added more tests for this and now I'm getting failures for SubjectKeyIdentifier but not IssuerAndSerialNumber (using 2.4.0-beta.61). I'll check v2.3.1 as soon as the meeting I'm in is over.

all tests pass on v2.3.1

Ah, got it.

The commit above depends on BouncyCastle 2.4.0-beta.61 @peterdettman What I ended up doing is writing unit tests for MimeKit that would encrypt using the System.Security backend and then verifying that...

@peterdettman what are your plans for releasing 2.4.0? I didn't realize that 2.3.1 fixed some security issues and so I'm getting requests to make a release with >= 2.3.1.

Hmmmm... > We started to get significantly more SmtpProtocolExceptions with the "unexpectedly disconnected" error message. Prior to 4.4.0, we rarely got SmtpProtocolException and they were mostly all SmtpCommandException. This sounds...

Okay, so there are essentially 5 locations where an SmtpProtocolException gets thrown: 3 of them are in the response parsing logic (but none of these say "unexpectedly disconnected") and the...

For `ServiceNotAuthenticatedException`, the `StatusCode` would always `530` and the `ResponseText` would be the same as the `Message` string.