MimeKitLite 1.0.13

dotnet add package MimeKitLite --version 1.0.13
NuGet\Install-Package MimeKitLite -Version 1.0.13
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="MimeKitLite" Version="1.0.13" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add MimeKitLite --version 1.0.13
#r "nuget: MimeKitLite, 1.0.13"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install MimeKitLite as a Cake Addin
#addin nuget:?package=MimeKitLite&version=1.0.13

// Install MimeKitLite as a Cake Tool
#tool nuget:?package=MimeKitLite&version=1.0.13

MimeKit is an Open Source library for creating and parsing MIME messages. It also supports parsing of Unix mbox files.

Unlike any other .NET MIME parser, MimeKit's parser does not need to parse string input nor does it use a TextReader. Instead, it parses raw byte streams, thus allowing it to better support undeclared 8bit text in headers as well as message bodies. It also means that MimeKit's parser is significantly faster than other .NET MIME parsers (more than 25x faster than OpenPOP.NET and about 75x faster than SharpMimeTools).

MimeKit's parser also uses a real tokenizer when parsing the headers rather than regex or string.Split() like most other .NET MIME parsers. This means that MimeKit is much more RFC-compliant than any other .NET MIME parser out there, including the commercial implementations.

In addition to having a far superior parser implementation, MimeKit's object tree is not a derivative of System.Net.Mail objects and thus does not suffer from System.Net.Mail's massive limitations or bugs.

API documentation can be found on the web at https://jstedfast.github.io/MimeKit/docs

For those that need SMTP, POP3 or IMAP support, check out https://github.com/jstedfast/MailKit

Product Compatible and additional computed target framework versions.
.NET net6.0-android was computed.  net7.0-android was computed.  net8.0-android was computed. 
.NET Framework net40 is compatible.  net403 was computed.  net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid is compatible. 
Universal Windows Platform uap was computed.  uap10.0 was computed. 
Windows Phone wpa81 is compatible. 
Xamarin.iOS xamarinios10 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

GitHub repositories (4)

Showing the top 4 popular GitHub repositories that depend on MimeKitLite:

Repository Stars
WireMock-Net/WireMock.Net
WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
cube0x0/KrbRelay
Framework for Kerberos relaying
ixre/cms
DDD 开源.NET CMS、跨平台, 兼容.NET Core和ASP.NET,支持Docker容器
Jericho/StrongGrid
Strongly typed library for the entire SendGrid v3 API, including webhooks
Version Downloads Last updated
1.0.13 196 4/11/2015
1.0.12 87 3/29/2015
1.0.11 105 3/21/2015
1.0.10 105 3/14/2015
1.0.9 81 3/8/2015
1.0.8 74 3/2/2015
1.0.7 198 2/17/2015
1.0.6.1 153 1/18/2015
1.0.6 46 1/18/2015
1.0.5 78 1/10/2015
1.0.4 57 1/8/2015
1.0.3 120 12/13/2014
1.0.2 92 12/5/2014
1.0.1 133 11/23/2014
1.0.0 166 10/15/2014

* Added a work-around for a bug in Thunderbird's multipart/related implementation. (issue #124)
* Improved MimeMessage.CreateFromMailMessage() a bit more to avoid creating empty From, Reply-To, To, Cc and/or Bcc headers.
* Modified the HeaderIdExtensions to only be available for the HeaderId enum values.

Note: If you are not yet ready to port your iOS application to the Unified API, you will need to stick with the 1.0.5 release. The Classic MonoTouch API is no longer supported.