0x1949 Team - FAZEMRX - MANAGER

Edit File: email.parser.html

<!DOCTYPE html>

<title>18.1.2. email.parser: Parsing email messages &#8212; Python 2.7.18 documentation</title>
 <link rel="stylesheet" type="text/css" href="../_static/pygments.css" />
 <link rel="stylesheet" type="text/css" href="../_static/classic.css" />
 
 <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
 <script src="../_static/jquery.js"></script>
 <script src="../_static/underscore.js"></script>
 <script src="../_static/doctools.js"></script>
 
 <script src="../_static/sidebar.js"></script>
 
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 2.7.18 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="18.1.3. email.generator: Generating MIME documents" href="email.generator.html" />
 <link rel="prev" title="18.1.1. email.message: Representing an email message" href="email.message.html" />
 <link rel="shortcut icon" type="image/png" href="../_static/py.png" />
 <link rel="canonical" href="file:///usr/share/doc/python2.7/html/library/email.parser.html" />
 <script type="text/javascript" src="../_static/copybutton.js"></script>

</head><body>
<div id="outdated-warning" style="padding: .5em; text-align: center; background-color: #FFBABA; color: #6A0E0E;">
 This document is for an old version of Python that is <a href="https://devguide.python.org/devcycle/#end-of-life-branches">no longer supported</a>.
 You should install the python3 and python3-doc packages and read the 
 <a href="file:///usr/share/doc/python3-doc/html/library/email.parser.html"> Python documentation for the Python3 version packaged in this release</a>.
</div>
 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="email.generator.html" title="18.1.3. email.generator: Generating MIME documents"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="email.message.html" title="18.1.1. email.message: Representing an email message"
 accesskey="P">previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">Python 2.7.18 documentation</a> &#187;
 </li>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="module-email.parser">
<h1>18.1.2. <a class="reference internal" href="#module-email.parser" title="email.parser: Parse flat text email messages to produce a message object structure."><code class="xref py py-mod docutils literal notranslate">email.parser</code></a>: Parsing email messages<a class="headerlink" href="#module-email.parser" title="Permalink to this headline">¶</a></h1>
Message object structures can be created in one of two ways: they can be created
from whole cloth by instantiating <a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects and
stringing them together via <a class="reference internal" href="email.message.html#email.message.Message.attach" title="email.message.Message.attach"><code class="xref py py-meth docutils literal notranslate">attach()</code></a> and
<a class="reference internal" href="email.message.html#email.message.Message.set_payload" title="email.message.Message.set_payload"><code class="xref py py-meth docutils literal notranslate">set_payload()</code></a> calls, or they
can be created by parsing a flat text representation of the email message.
The <a class="reference internal" href="email.html#module-email" title="email: Package supporting the parsing, manipulating, and generating email messages, including MIME documents."><code class="xref py py-mod docutils literal notranslate">email</code></a> package provides a standard parser that understands most email
document structures, including MIME documents. You can pass the parser a string
or a file object, and the parser will return to you the root
<a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> instance of the object structure. For simple,
non-MIME messages the payload of this root object will likely be a string
containing the text of the message. For MIME messages, the root object will
return <code class="docutils literal notranslate">True</code> from its <a class="reference internal" href="email.message.html#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> method, and
the subparts can be accessed via the <a class="reference internal" href="email.message.html#email.message.Message.get_payload" title="email.message.Message.get_payload"><code class="xref py py-meth docutils literal notranslate">get_payload()</code></a>
and <a class="reference internal" href="email.message.html#email.message.Message.walk" title="email.message.Message.walk"><code class="xref py py-meth docutils literal notranslate">walk()</code></a> methods.
There are actually two parser interfaces available for use, the classic
<a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> API and the incremental <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> API. The classic
<a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> API is fine if you have the entire text of the message in memory
as a string, or if the entire message lives in a file on the file system.
<a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> is more appropriate for when you’re reading the message from
a stream which might block waiting for more input (e.g. reading an email message
from a socket). The <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> can consume and parse the message
incrementally, and only returns the root object when you close the parser <a class="footnote-reference brackets" href="#id2" id="id1">1</a>.
Note that the parser can be extended in limited ways, and of course you can
implement your own parser completely from scratch. There is no magical
connection between the <a class="reference internal" href="email.html#module-email" title="email: Package supporting the parsing, manipulating, and generating email messages, including MIME documents."><code class="xref py py-mod docutils literal notranslate">email</code></a> package’s bundled parser and the
<a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> class, so your custom parser can create message
object trees any way it finds necessary.
<section id="feedparser-api">
<h2>18.1.2.1. FeedParser API<a class="headerlink" href="#feedparser-api" title="Permalink to this headline">¶</a></h2>
<div class="versionadded">
New in version 2.4.
</div>
The <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>, imported from the <code class="xref py py-mod docutils literal notranslate">email.feedparser</code> module,
provides an API that is conducive to incremental parsing of email messages, such
as would be necessary when reading the text of an email message from a source
that can block (e.g. a socket). The <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> can of course be used
to parse an email message fully contained in a string or a file, but the classic
<a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> API may be more convenient for such use cases. The semantics
and results of the two parser APIs are identical.
The <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>’s API is simple; you create an instance, feed it a bunch
of text until there’s no more to feed it, then close the parser to retrieve the
root message object. The <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> is extremely accurate when parsing
standards-compliant messages, and it does a very good job of parsing
non-compliant messages, providing information about how a message was deemed
broken. It will populate a message object’s defects attribute with a list of
any problems it found in a message. See the <a class="reference internal" href="email.errors.html#module-email.errors" title="email.errors: The exception classes used by the email package."><code class="xref py py-mod docutils literal notranslate">email.errors</code></a> module for the
list of defects that it can find.
Here is the API for the <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>:
<dl class="py class">
<dt class="sig sig-object py" id="email.parser.FeedParser">
class email.parser.FeedParser([_factory])<a class="headerlink" href="#email.parser.FeedParser" title="Permalink to this definition">¶</a></dt>
<dd>Create a <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> instance. Optional _factory is a no-argument
callable that will be called whenever a new message object is needed. It
defaults to the <a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">email.message.Message</code></a> class.
<dl class="py method">
<dt class="sig sig-object py" id="email.parser.FeedParser.feed">
feed(data)<a class="headerlink" href="#email.parser.FeedParser.feed" title="Permalink to this definition">¶</a></dt>
<dd>Feed the <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> some more data. data should be a string
containing one or more lines. The lines can be partial and the
<a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> will stitch such partial lines together properly. The
lines in the string can have any of the common three line endings,
carriage return, newline, or carriage return and newline (they can even be
mixed).
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.parser.FeedParser.close">
close()<a class="headerlink" href="#email.parser.FeedParser.close" title="Permalink to this definition">¶</a></dt>
<dd>Closing a <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a> completes the parsing of all previously fed
data, and returns the root message object. It is undefined what happens
if you feed more data to a closed <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>.
</dd></dl>

</dd></dl>

</section>
<section id="parser-class-api">
<h2>18.1.2.2. Parser class API<a class="headerlink" href="#parser-class-api" title="Permalink to this headline">¶</a></h2>
The <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> class, imported from the <a class="reference internal" href="#module-email.parser" title="email.parser: Parse flat text email messages to produce a message object structure."><code class="xref py py-mod docutils literal notranslate">email.parser</code></a> module,
provides an API that can be used to parse a message when the complete contents
of the message are available in a string or file. The <a class="reference internal" href="#module-email.parser" title="email.parser: Parse flat text email messages to produce a message object structure."><code class="xref py py-mod docutils literal notranslate">email.parser</code></a>
module also provides a second class, called <code class="xref py py-class docutils literal notranslate">HeaderParser</code> which can be
used if you’re only interested in the headers of the message.
<code class="xref py py-class docutils literal notranslate">HeaderParser</code> can be much faster in these situations, since it does not
attempt to parse the message body, instead setting the payload to the raw body
as a string. <code class="xref py py-class docutils literal notranslate">HeaderParser</code> has the same API as the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a>
class.
<dl class="py class">
<dt class="sig sig-object py" id="email.parser.Parser">
class email.parser.Parser([_class])<a class="headerlink" href="#email.parser.Parser" title="Permalink to this definition">¶</a></dt>
<dd>The constructor for the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> class takes an optional argument
_class. This must be a callable factory (such as a function or a class), and
it is used whenever a sub-message object needs to be created. It defaults to
<a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> (see <a class="reference internal" href="email.message.html#module-email.message" title="email.message: The base class representing email messages."><code class="xref py py-mod docutils literal notranslate">email.message</code></a>). The factory will
be called without arguments.
The optional strict flag is ignored.
<div class="deprecated">
Deprecated since version 2.4: Because the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> class is a backward compatible API wrapper
around the new-in-Python 2.4 <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>, all parsing is
effectively non-strict. You should simply stop passing a strict flag to
the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> constructor.
</div>
<div class="versionchanged">
Changed in version 2.2.2: The strict flag was added.
</div>
<div class="versionchanged">
Changed in version 2.4: The strict flag was deprecated.
</div>
The other public <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> methods are:
<dl class="py method">
<dt class="sig sig-object py" id="email.parser.Parser.parse">
parse(fp[, headersonly])<a class="headerlink" href="#email.parser.Parser.parse" title="Permalink to this definition">¶</a></dt>
<dd>Read all the data from the file-like object fp, parse the resulting
text, and return the root message object. fp must support both the
<a class="reference internal" href="io.html#io.TextIOBase.readline" title="io.TextIOBase.readline"><code class="xref py py-meth docutils literal notranslate">readline()</code></a> and the <a class="reference internal" href="io.html#io.TextIOBase.read" title="io.TextIOBase.read"><code class="xref py py-meth docutils literal notranslate">read()</code></a>
methods on file-like objects.
The text contained in fp must be formatted as a block of <a class="rfc reference external" href="https://tools.ietf.org/html/rfc2822.html">RFC 2822</a>
style headers and header continuation lines, optionally preceded by an
envelope header. The header block is terminated either by the end of the
data or by a blank line. Following the header block is the body of the
message (which may contain MIME-encoded subparts).
Optional headersonly is a flag specifying whether to stop parsing after
reading the headers or not. The default is <code class="docutils literal notranslate">False</code>, meaning it parses
the entire contents of the file.
<div class="versionchanged">
Changed in version 2.2.2: The headersonly flag was added.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.parser.Parser.parsestr">
parsestr(text[, headersonly])<a class="headerlink" href="#email.parser.Parser.parsestr" title="Permalink to this definition">¶</a></dt>
<dd>Similar to the <a class="reference internal" href="#email.parser.Parser.parse" title="email.parser.Parser.parse"><code class="xref py py-meth docutils literal notranslate">parse()</code></a> method, except it takes a string object
instead of a file-like object. Calling this method on a string is exactly
equivalent to wrapping text in a <a class="reference internal" href="stringio.html#StringIO.StringIO" title="StringIO.StringIO"><code class="xref py py-class docutils literal notranslate">StringIO</code></a> instance first and
calling <a class="reference internal" href="#email.parser.Parser.parse" title="email.parser.Parser.parse"><code class="xref py py-meth docutils literal notranslate">parse()</code></a>.
Optional headersonly is as with the <a class="reference internal" href="#email.parser.Parser.parse" title="email.parser.Parser.parse"><code class="xref py py-meth docutils literal notranslate">parse()</code></a> method.
<div class="versionchanged">
Changed in version 2.2.2: The headersonly flag was added.
</div>
</dd></dl>

</dd></dl>

Since creating a message object structure from a string or a file object is such
a common task, two functions are provided as a convenience. They are available
in the top-level <a class="reference internal" href="email.html#module-email" title="email: Package supporting the parsing, manipulating, and generating email messages, including MIME documents."><code class="xref py py-mod docutils literal notranslate">email</code></a> package namespace.
<dl class="py function">
<dt class="sig sig-object py" id="email.message_from_string">
email.message_from_string(s[, _class[, strict]])<a class="headerlink" href="#email.message_from_string" title="Permalink to this definition">¶</a></dt>
<dd>Return a message object structure from a string. This is exactly equivalent to
<code class="docutils literal notranslate">Parser().parsestr(s)</code>. Optional _class and strict are interpreted as
with the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> class constructor.
<div class="versionchanged">
Changed in version 2.2.2: The strict flag was added.
</div>
</dd></dl>

<dl class="py function">
<dt class="sig sig-object py" id="email.message_from_file">
email.message_from_file(fp[, _class[, strict]])<a class="headerlink" href="#email.message_from_file" title="Permalink to this definition">¶</a></dt>
<dd>Return a message object structure tree from an open file object. This is
exactly equivalent to <code class="docutils literal notranslate">Parser().parse(fp)</code>. Optional _class and strict
are interpreted as with the <a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> class constructor.
<div class="versionchanged">
Changed in version 2.2.2: The strict flag was added.
</div>
</dd></dl>

Here’s an example of how you might use this at an interactive Python prompt:
<div class="highlight-default notranslate"><div class="highlight"><pre>&gt;&gt;&gt; import email
&gt;&gt;&gt; msg = email.message_from_string(myString)
</pre></div>
</div>
</section>
<section id="additional-notes">
<h2>18.1.2.3. Additional notes<a class="headerlink" href="#additional-notes" title="Permalink to this headline">¶</a></h2>
Here are some notes on the parsing semantics:
<ul class="simple">
<li>Most non-multipart type messages are parsed as a single message
object with a string payload. These objects will return <code class="docutils literal notranslate">False</code> for
<a class="reference internal" href="email.message.html#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a>. Their
<a class="reference internal" href="email.message.html#email.message.Message.get_payload" title="email.message.Message.get_payload"><code class="xref py py-meth docutils literal notranslate">get_payload()</code></a> method will return a string object.</li>
<li>All multipart type messages will be parsed as a container message
object with a list of sub-message objects for their payload. The outer
container message will return <code class="docutils literal notranslate">True</code> for
<a class="reference internal" href="email.message.html#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> and their
<a class="reference internal" href="email.message.html#email.message.Message.get_payload" title="email.message.Message.get_payload"><code class="xref py py-meth docutils literal notranslate">get_payload()</code></a> method will return the list of
<a class="reference internal" href="email.message.html#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> subparts.</li>
<li>Most messages with a content type of message/* (e.g.
message/delivery-status and message/rfc822) will also be
parsed as container object containing a list payload of length 1. Their
<a class="reference internal" href="email.message.html#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> method will return <code class="docutils literal notranslate">True</code>.
The single element in the list payload will be a sub-message object.</li>
<li>Some non-standards compliant messages may not be internally consistent about
their multipart-edness. Such messages may have a
Content-Type header of type multipart, but their
<a class="reference internal" href="email.message.html#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> method may return <code class="docutils literal notranslate">False</code>.
If such messages were parsed with the <a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>,
they will have an instance of the
<code class="xref py py-class docutils literal notranslate">MultipartInvariantViolationDefect</code> class in their
defects attribute list. See <a class="reference internal" href="email.errors.html#module-email.errors" title="email.errors: The exception classes used by the email package."><code class="xref py py-mod docutils literal notranslate">email.errors</code></a> for details.</li>
</ul>
Footnotes
<dl class="footnote brackets">
<dt class="label" id="id2"><a class="fn-backref" href="#id1">1</a></dt>
<dd>As of email package version 3.0, introduced in Python 2.4, the classic
<a class="reference internal" href="#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> was re-implemented in terms of the
<a class="reference internal" href="#email.parser.FeedParser" title="email.parser.FeedParser"><code class="xref py py-class docutils literal notranslate">FeedParser</code></a>, so the semantics and results are
identical between the two parsers.
</dd>
</dl>
</section>
</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">18.1.2. <code class="xref py py-mod docutils literal notranslate">email.parser</code>: Parsing email messages</a><ul>
<li><a class="reference internal" href="#feedparser-api">18.1.2.1. FeedParser API</a></li>
<li><a class="reference internal" href="#parser-class-api">18.1.2.2. Parser class API</a></li>
<li><a class="reference internal" href="#additional-notes">18.1.2.3. Additional notes</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="email.message.html"
 title="previous chapter">18.1.1. <code class="xref py py-mod docutils literal notranslate">email.message</code>: Representing an email message</a>
 <h4>Next topic</h4>
 <a href="email.generator.html"
 title="next chapter">18.1.3. <code class="xref py py-mod docutils literal notranslate">email.generator</code>: Generating MIME documents</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../_sources/library/email.parser.rst.txt"
 rel="nofollow">Show Source</a></li>
 </ul>
 </div>
<div id="searchbox" style="display: none" role="search">
 <h3 id="searchlabel">Quick search</h3>
 <div class="searchformwrapper">
 <form class="search" action="../search.html" method="get">
 <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
 <input type="submit" value="Go" />
 </form>
 </div>
</div>
<script>$('#searchbox').show(0);</script>
 </div>
 </div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="email.generator.html" title="18.1.3. email.generator: Generating MIME documents"
 >next</a> |</li>
 <li class="right" >
 <a href="email.message.html" title="18.1.1. email.message: Representing an email message"
 >previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">Python 2.7.18 documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="netdata.html" >18. Internet Data Handling</a> &#187;</li>
 <li class="nav-item nav-item-3"><a href="email.html" >18.1. <code class="xref py py-mod docutils literal notranslate">email</code> — An email and MIME handling package</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href="">18.1.2. <code class="xref py py-mod docutils literal notranslate">email.parser</code>: Parsing email messages</a></li> 
 </ul>
 </div> 
 <div class="footer">
 &copy; <a href="../copyright.html">Copyright</a> 1990-2024, Python Software Foundation.
 
 The Python Software Foundation is a non-profit corporation.
 <a href="https://www.python.org/psf/donations/">Please donate.</a>
 
 Last updated on November 21, 2024.
 <a href="../bugs.html">Found a bug</a>?
 
 Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 4.3.2.
 </div>

</body>
</html>