MailKit VS platform-compat

Third, Send-MailMessage has been deprecated. Try MailKit instead. To be honest, though, I'm yet to find time and test it myself.

Microsoft doesn't recommend SmtpClient for new development. We've been using MailKit for years.

Looks like Mailkit is the way to go for open source solutions.

Microsoft recommends MailKit in the SmtpClient docs

Jeffrey Stedfast is on reddit and is an ancap and works for Microsoft as a Senior Engineer. His Mimekit/Mailkit library for C# is recommended in the official Microsoft documentation for sending email instead of the one included by default.

TIL. Looks like the deprecation note recommends MailKit.

You could even do this with your own GMail Client. Design yourself some sweet UI, and use a simple library like: MailKit and wrap your own service around that, to get your emails. And maybe implement some features like writing yourself reminders for important mails, a few dashboards where you can drag around mails Kanban style.

recommends you use MailKit as alternate

DotNet offers the SecureString class to keep a string encrypted in Memory, but as long as the OS does not natively support this concept, the only advantage is that it resides in memory for a shorter time, the disadvantage is that SecureStrings are easier to search for.

Note the KeePass's resistance to the attack mentioned depends on the security of .NET's secure string, which, here's what Microsoft has to say about it (https://github.com/dotnet/platform-compat/blob/master/docs/D...)

As for KeePassXC, last I checked it didn't even bother.

TIL. Looks like the deprecation note recommends MailKit.

Well of course, but it does have to be passed to the module that generates the hashes AD uses in the first place. And as I said, the standard password reset screen is bound to store the password in plain text somewhere as well.

This won’t help you with your question, but I figured I should warn against using send-mailmessage.

points you here.

Some of the reasons for not using Hashtable or other non-generic collection types are outlined here. That's why Microsoft doesn't recommend their usage in new implementations across all of its API documentation.

And if you really want to be secure you need to something better than a SecureString: https://github.com/dotnet/platform-compat/blob/master/docs/DE0001.md