\n \n A T:MimeKit.TextPart is a leaf-node\n MIME part with a text media-type. The first argument to the TextPart constructor\n specifies the media-subtype, in this case, plain . Another\n media subtype you are probably familiar with is the html \n subtype. Some other examples include enriched ,\n rtf , and xml .\n \n \n The P:MimeKit.TextPart.Text property\n is the easiest way to both get and set the string content of the MIME part.\n \n \n \n Of course, that is just a simple example. A lot of modern mail clients such as Outlook\n or Thunderbird will send out both a text/html and a\n text/plain version of the message text. To do this, you'd create a\n T:MimeKit.TextPart for each part and then\n add them to a multipart/alternative like so:\n \n \n \n \n System.Text.Encoding.RegisterProvider (System.Text.CodePagesEncodingProvider.Instance);\n \n \n System.Text.Encoding.RegisterProvider (System.Text.CodePagesEncodingProvider.Instance);\n \n \n <configuration>\n <runtime>\n <assemblyBinding xmlns=\"urn:schemas-microsoft-com:asm.v1\">\n <dependentAssembly>\n <assemblyIdentity name=\"System.Runtime.CompilerServices.Unsafe\" publicKeyToken=\"b03f5f7f11d50a3a\" culture=\"neutral\"/>\n <bindingRedirect oldVersion=\"0.0.0.0-6.0.0.0\" newVersion=\"6.0.0.0\" />\n </dependentAssembly>\n </assemblyBinding>\n </runtime>\n </configuration>\n \n - \n
\n using (var client = new SmtpClient ()) {\n client.ServerCertificateValidationCallback = (s,c,h,e) => true;\n\n client.Connect (hostName, port, SecureSocketOptions.Auto);\n\n // ...\n }\n \n \n bool MyServerCertificateValidationCallback (object sender, X509Certificate certificate, X509Chain chain, SslPolicyErrors sslPolicyErrors)\n {\n if (sslPolicyErrors == SslPolicyErrors.None)\n return true;\n\n // Note: The following code casts to an X509Certificate2 because it's easier to get the\n // values for comparison, but it's possible to get them from an X509Certificate as well.\n if (certificate is X509Certificate2 certificate2) {\n var cn = certificate2.GetNameInfo (X509NameType.SimpleName, false);\n var fingerprint = certificate2.Thumbprint;\n var serial = certificate2.SerialNumber;\n var issuer = certificate2.Issuer;\n\n return cn == \"imap.gmail.com\" && issuer == \"CN=GTS CA 1O1, O=Google Trust Services, C=US\" &&\n serial == \"00BABE95B167C9ECAF08000000006065B6\" &&\n fingerprint == \"E79A011EF55EEC72D2B7E391D193761372796836\";\n }\n\n return false;\n }\n \n \n using (var client = new SmtpClient ()) {\n client.CheckCertificateRevocation = false;\n\n client.Connect (hostName, port, SecureSocketOptions.Auto);\n\n // ...\n }\n \n \n using (var client = new SmtpClient ()) {\n // Allow SSLv3.0 and all versions of TLS\n client.SslProtocols = SslProtocols.Ssl3 | SslProtocols.Tls | SslProtocols.Tls11 | SslProtocols.Tls12 | SslProtocols.Tls13;\n\n client.Connect (\"smtp.gmail.com\", 465, true);\n\n // ...\n }\n \n \n // log to a file called 'imap.log'\n var client = new ImapClient (new ProtocolLogger (\"imap.log\"));\n\n // log to standard output (i.e. the console)\n var client = new ImapClient (new ProtocolLogger (Console.OpenStandardOutput ()));\n \n - \n
- \n
\nusing (var client = new ImapClient ()) {\n client.Connect (\"imap.gmail.com\", 993, SecureSocketOptions.SslOnConnect);\n client.Authenticate (\"user@gmail.com\", \"app-specific-password\");\n \n // do stuff...\n \n client.Disconnect (true);\n}\n \n \nconst string GMailAccount = \"username@gmail.com\";\n\nvar clientSecrets = new ClientSecrets {\n ClientId = \"XXX.apps.googleusercontent.com\",\n ClientSecret = \"XXX\"\n};\n\nvar codeFlow = new GoogleAuthorizationCodeFlow (new GoogleAuthorizationCodeFlow.Initializer {\n // Cache tokens in ~/.local/share/google-filedatastore/CredentialCacheFolder on Linux/Mac\n DataStore = new FileDataStore (\"CredentialCacheFolder\", false),\n Scopes = new [] { \"https://mail.google.com/\" },\n ClientSecrets = clientSecrets\n});\n\nvar codeReceiver = new LocalServerCodeReceiver ();\nvar authCode = new AuthorizationCodeInstalledApp (codeFlow, codeReceiver);\nvar credential = await authCode.AuthorizeAsync (GMailAccount, CancellationToken.None);\n\nif (authCode.ShouldRequestAuthorizationCode (credential.Token))\n await credential.RefreshTokenAsync (CancellationToken.None);\n\nvar oauth2 = new SaslMechanismOAuth2 (credential.UserId, credential.Token.AccessToken);\n\nusing (var client = new ImapClient ()) {\n await client.ConnectAsync (\"imap.gmail.com\", 993, SecureSocketOptions.SslOnConnect);\n await client.AuthenticateAsync (oauth2);\n await client.DisconnectAsync (true);\n}\n \n \n \n A simpler way to construct messages with attachments is to take advantage of the\n T:MimeKit.BodyBuilder class.\n \n \n \n For more information, see Creating Messages.\n \n - \n
\nmultipart/alternative\n text/plain\n text/html
\nmultipart/alternative\n text/plain\n multipart/related\n text/html\n image/jpeg\n image/png
\nmultipart/mixed\n text/plain\n application/octet-stream\n application/zip
\nmultipart/mixed\n multipart/alternative\n text/plain\n text/html\n application/octet-stream\n application/zip
\nmultipart/mixed\n multipart/alternative\n text/plain\n multipart/related\n text/html\n image/jpeg\n image/png\n application/octet-stream\n application/zip
\nvar attachments = message.BodyParts.OfType<MimePart> ().Where (part => !string.IsNullOrEmpty (part.FileName));\n \n \n And the way you'd use this visitor might look something like this: \n \n \n Once you've rendered the message using the above technique, you'll have a list of attachments\n that were not used, even if they did not match the simplistic criteria used by the\n P:MimeKit.MimeMessage.Attachments \n property.\n \n message.WriteTo (\"message.eml\");\n \n// clone the default formatting options\nvar format = FormatOptions.Default.Clone ();\n\n// override the line-endings to be DOS no matter what platform we are on\nformat.NewLineFormat = NewLineFormat.Dos;\n\nmessage.WriteTo (format, \"message.eml\");\n \n \nforeach (var mailbox in message.To.Mailboxes)\n Console.WriteLine (\"{0}'s email address is {1}\", mailbox.Name, mailbox.Address);\n \n \nParameter param;\n\nif (attachment.ContentDisposition.Parameters.TryGetValue (\"filename\", out param))\n param.EncodingMethod = ParameterEncodingMethod.Rfc2047;\n \n \nvar options = FormatOptions.Default.Clone ();\noptions.ParameterEncodingMethod = ParameterEncodingMethod.Rfc2047;\n\nmessage.WriteTo (options, stream);\n \n \n \n To deal with these kinds of messages, MimeKit's\n T:MimeKit.Cryptography.OpenPgpContext \n includes a\n \n M:MimeKit.Cryptography.OpenPgpContext.DecryptTo(System.IO.Stream,System.IO.Stream,System.Threading.CancellationToken)\n \n method which can be used to get the raw decrypted stream.\n \n \n The method variant that has a\n T:MimeKit.Cryptography.DigitalSignatureCollection \n output parameter is useful in cases where the encrypted PGP blurb is also digitally signed,\n allowing you to get your hands on the list of digital signatures in order for you to verify\n each of them.\n \n \n To decrypt the sample message above, you could use the following code snippet:\n \n \n - \n
\n \n But what if you wanted to reply to a message and quote the HTML formatting of the original message\n body (assuming it has an HTML body) while still including the embedded images?\n \n \n This gets a bit more complicated, but it's still doable...\n \n \n The first thing we'd need to do is implement our own T:MimeKit.MimeVisitor \n to handle this:\n \n \n \n \n \n To forward a message by inlining the original message's text content, you can do something like this:\n \n \n \nforeach (var uid in folder.Search (SearchQuery.NotSeen)) {\n var message = folder.GetMessage (uid);\n}\n \n \n \n If the multipart/form-data HTTP response is expected to be large and you do\n not wish for the content to be read into memory, you can use the following\n approach:\n \n \n - \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
\n \n ![\"Click](\"https://www.paypal.com/en_US/i/btn/x-click-but21.gif\")
\n \n
\nmultipart/alternative\n text/plain\n text/html
\nmultipart/alternative\n text/plain\n multipart/related\n text/html\n image/jpeg\n video/mp4\n image/png
\n \n A second way, which is a bit cleaner and doesn't require recursive methods, is\n to use a T:MimeKit.MimeIterator :\n \n \n And finally, for those that prefer to use the\n \n visitor pattern \n http://en.wikipedia.org/wiki/Visitor_pattern \n _blank \n , MimeKit includes the\n T:MimeKit.MimeVisitor class for\n visiting each node in the MIME tree structure. For example, the following\n MimeVisitor subclass could be used to generate HTML to be rendered by a\n browser control (such as \n T:System.Windows.Forms.WebBrowser\n ):\n \n \n And the way you'd use this visitor might look something like this: \n \n \n \n \n You can also get access to the original raw content by \"opening\" the\n P:MimeKit.MimePart.Content .\n This might be useful if you want to pass the content off to a UI control that\n can do its own loading from a stream.\n \n \n \n There are a number of useful filters that can be applied to a\n T:MimeKit.IO.FilteredStream , so if you\n find this type of interface appealing, I would suggest taking a look at the available\n filters in the N:MimeKit.IO.Filters \n namespace or even write your own! The possibilities are limited only by your\n imagination.\n \n \n \n To register your class, you can use the following code snippet:\n \n \n \n Now you are ready to encrypt, decrypt, sign and verify messages using PGP!\n \n \n \n \n When you know that you will be encrypting a message, it may be a good idea to use\n a T:MimeKit.Cryptography.SecureMailboxAddress \n instead of a T:MimeKit.MailboxAddress \n for each of the recipients, allowing you to specify the unique fingerprint of each\n recipient's PGP key.\n \n \n \n \n \n You can also do your own PGP key lookups instead of relying on email addresses\n to match up with the user's secret key.\n \n \n \n \n \n To register your class, you can use the following code snippet:\n \n \n \n Now you are ready to encrypt, decrypt, sign and verify messages using S/MIME!\n \n \n \n \n When you know that you will be encrypting a message, it may be a good idea to use\n a T:MimeKit.Cryptography.SecureMailboxAddress \n instead of a T:MimeKit.MailboxAddress \n for each of the recipients, allowing you to specify the unique fingerprint of each\n recipient's X.509 certificate.\n \n \n \n \n \n You can also do your own certificate lookups instead of relying on email addresses\n to match up with the user's certificate.\n \n \n \n You can also choose to digitally sign a\n T:MimeKit.MimeEntity using the\n application/pkcs7-mime format using\n \n Overload:MimeKit.Cryptography.ApplicationPkcs7Mime.Sign\n \n \n \n \n \n When you know that you will be signing a message, it may be a good idea to use\n a T:MimeKit.Cryptography.SecureMailboxAddress \n instead of a T:MimeKit.MailboxAddress \n for the sender, allowing you to specify the unique fingerprint of the sender's\n X.509 certificate.\n \n \n \n \n It should be noted, however, that while most S/MIME clients will use the preferred\n multipart/signed approach, it is possible that you may encounter an\n application/pkcs7-mime part with an smime-type \n parameter set to signed-data . Luckily, MimeKit can handle this\n format as well:\n \n \n Hey Alice,
\n
What are you up to this weekend? Monica is throwing one of her parties on\nSaturday and I was hoping you could make it.
\n
Will you be my +1?
\n
-- Joey
\n
\n\t\t\t\t\thtmlWriter.WriteEndTag (HtmlTagId.BlockQuote);\n\n\t\t\t\t\t// pass the