MailBee.NET Security components enable .NET applications to sign, verify, encrypt, decrypt e-mails, work with DomainKeys, 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) in both dedicated and STARTTLS modes, use impersonation. DomainKeys and SSL/TLS support is available at no additional cost, only the corresponding MailBee.NET SMTP/POP3/IMAP license is required.

The key features of the component:

• 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 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). It's shipped in 3 versions: generic .NET 1.1 (for legacy applications), optimized for .NET 2.0 (including .NET 3.0, 3.5 and above) and .NET Compact Framework version (for Windows Mobile platform). Windows Mobile version, however, cannot support S/MIME and DomainKeys due to .NET Compact Framework and OS limitations.

Samples are available for C# and VB.NET, WinForms and ASP.NET, .NET 2.0+ and .NET 1.1.

Documentation: integrated into Visual Studio 2003/2005/2008, .CHM file, Online.

Developer license permits royalty-free distribution of MailBee.NET.dll.