Aegis Implicit Mail is a free and open source library which is designed to provide fast and developer friendly API to send emails using SMTP ports.
Binaries are available in the form of NuGet package:
https://www.nuget.org/packages/AIM
Please check http://pki.tools/aim.html as well
AIM Supports :
* None Ssl Mails
* Implicit Ssl Mails
* Explicit Ssl Mails
* Smtp Connection test
* Detect Ssl type of mail server
* Attachments for MIME and S/MIME message.
* In-line attachment and separate file attachment
* All content types and mimes
* SMIME , Signed and Encrypted mails
In an integrated way
Sadly, Microsoft.Net.Mail Ssl Mails does not support Implicit Ssl Mail and it is still used by many servers, including port 465 of Gmail here AIM comes to make a readable and fast alternative to send your smtp mails.
For unicode issues please refer to https://sourceforge.net/p/netimplicitssl/tickets/4/ . We really appriciate any help in testing of different encodings
Features
- Support for both of Smime and Mime Messages
- Easy to use and well designed, easy to migrate from System.Net.Mail
- Support for Signed and/or encrypted mail
- Supports Ssl Type detection (Detects if Mail server is using Implicit (SSL) or Explicit (TLS) smtp)
- Support Base64, PlainText and default credential Athentication
- Asynchronous Mail Sending
- Support None Ssl Mails
- Support Inline and Attached Attachments.
- Signed and Encrypted attachments
- Fast and reliable
- Made by developers for developers
- Test Connection Settings
- Auto Detection of Ssl Type
- Support Office 365
- Support display name
License
GNU General Public License version 2.0 (GPLv2)User Reviews
-
Attachments do not work. Mail servers throw the error "550 Maximum line length exceeded (see RFC 5322 2.1.1)" even if attachments are specified as attached and not inline. Is there anything I could try?
-
Microsoft refused to fix implicit SSL in their SmtpClient. AIM is a great replacement for it, that solves this problem.
-
good work :)
-
Excellent
-
Created based on standard windows mail