<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mime on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/mime/</link>
    <description>Recent content in Mime on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/mime/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Email MIME Parsing Libraries: mailparser vs MimeKit vs GMime vs Python email</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-email-mime-parsing-libraries-mailparser-mimekit-gmime/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-email-mime-parsing-libraries-mailparser-mimekit-gmime/</guid>
      <description>&lt;p&gt;Email communication remains the backbone of enterprise messaging, and behind every email client or server lies a critical component: the MIME (Multipurpose Internet Mail Extensions) parser. MIME parsers decode raw email bytes into structured objects — extracting attachments, handling character encodings, verifying signatures, and reconstructing messages from quoted-printable or base64 representations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
