MailBee.NET Security 10.0
ailBee.NET Security classes 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 Windows impersonation. FIPS 140-2 compatible.
These classes are intended to be used with other MailBee.NET components. MailBee.NET Security acts as a set of helper classes which adds more features to the core MailBee.NET functionality.
DomainKeys/DKIM and SSL/TLS support is available at no additional cost, only the corresponding MailBee.NET SMTP/POP3/IMAP license is required. Using certificates and S/MIME does require separate MailBee.NET Security license.
The key features:
- SSL (TLS) connections with mail servers;
- 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;
- 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/4.6 (including Client Profile), both 32/64 bit, Xamarin Mono, iOS, Android.
Samples are available for C# and VB.NET, WinForms and ASP.NET.
Royalty-free distribution allowed.
Requirements
Changes: 10.0
- Xamarin support
- TLS 1.1/1.2 support
