Wrap exceptions thrown from System.Security.Cryptography
I get this exception when attempting to login in to an SMTP server using the Rebex.Net.SmtpAuthentication.Auto authentication method on a machine that has FIPS compliance turned on via Windows. This disables the MD5 hashing algorithm and causes the Smtp.Login method to throw undocumented exceptions.
It might be even nicer if the Rebex.Net.SmtpAuthentication.Auto would detect that MD5 hashing is not available on the sending machine (even though it is an available login method on the server) and negotiate to the next lower level of authentication security.
But my real complain is that a System.Reflection.TargetInvokationException is thrown from this method. I shouldn't have to know to catch that.
The fix has been released as a part of 2012 R3. More info about release 2012 R3 can be found at this blogpost
http://blog.rebex.net/news/archive/2012/11/01/version-2012-r3.aspx.
-
Tomáš Knopp commented
Hello Derek, thank you for your feedback. Both of your points are perfectly valid, we are going to release the fix for this in the next release which is already quite near. We will post here as soon as it will be out.