MailBee.NET Security components enable .NET applications to sign, verify, encrypt, decrypt e-mails, work with DomainKeys/DKIM, S/MIME, SSL/TLS, public and private certificates (including PFX), use MailBee.NET SMTP/POP3/IMAP components to connect to secure mail servers (like Gmail and MS Exchange) in both dedicated and STARTTLS modes, use impersonation.

DomainKeys/DKIM and SSL/TLS support is available at no additional cost, only the corresponding MailBee.NET SMTP/POP3/IMAP license is required. Using ceritificates and S/MIME does require separate MailBee.NET Security license.

The key features:

SSL (TLS) connections with mail servers, up to TLS 1.2;
supports connections to dedicated SSL ports and to regular ports (STARTTLS);
client and server certificates;
validation of the server certificate;
certificate and certificate store management (reading from or saving into a file, registry, memory, etc);
enumerating and finding certificates in certificate stores;
supports private certificates and PFX format;
digital signatures;
SHA1, SHA256, AES-128, AES-256 supported;
S/MIME features: sign, verify, encrypt, decrypt messages;
security algorithms, CryptoServiceProviders, etc;
DomainKeys anti-spam technology (creating and verifying DomainKeys and DKIM signatures);
impersonation;
integration with Smtp, Pop3, Imap and MailMessage components of MailBee.NET Objects suite;
error handling features.

The assembly DLL is completely written in C# (no external COM dependencies).

Supports .NET 2.0/3.0/3.5/4.0/4.5+ (Client Profile compatible). Limited support in .NET Core 1.0/1.1, Xamarin (Android/iOS), UWP (Universal Windows). Can be used in desktop, console and ASP.NET applications developed in C#/VB.NET/etc.

Samples: C# and VB.NET, WinForms and ASP.NET, .NET 2.0+ and .NET 4.5+.

Royalty-free distribution allowed.