### 导航 - [索引](../genindex.xhtml "总目录") - [模块](../py-modindex.xhtml "Python 模块索引") | - [下一页](email.message.xhtml "email.message: Representing an email message") | - [上一页](netdata.xhtml "互联网数据处理") | -  - [Python](https://www.python.org/) » - zh\_CN 3.7.3 [文档](../index.xhtml) » - [Python 标准库](index.xhtml) » - [互联网数据处理](netdata.xhtml) » - $('.inline-search').show(0); | # [`email`](#module-email "email: Package supporting the parsing, manipulating, and generating email messages.") --- 电子邮件与 MIME 处理包 **源码:** [Lib/email/\_\_init\_\_.py](https://github.com/python/cpython/tree/3.7/Lib/email/__init__.py) \[https://github.com/python/cpython/tree/3.7/Lib/email/\_\_init\_\_.py\] - - - - - - The [`email`](#module-email "email: Package supporting the parsing, manipulating, and generating email messages.") package is a library for managing email messages. It is specifically *not* designed to do any sending of email messages to SMTP ([**RFC 2821**](https://tools.ietf.org/html/rfc2821.html) \[https://tools.ietf.org/html/rfc2821.html\]), NNTP, or other servers; those are functions of modules such as [`smtplib`](smtplib.xhtml#module-smtplib "smtplib: SMTP protocol client (requires sockets).") and [`nntplib`](nntplib.xhtml#module-nntplib "nntplib: NNTP protocol client (requires sockets)."). The [`email`](#module-email "email: Package supporting the parsing, manipulating, and generating email messages.") package attempts to be as RFC-compliant as possible, supporting [**RFC 5233**](https://tools.ietf.org/html/rfc5233.html) \[https://tools.ietf.org/html/rfc5233.html\] and [**RFC 6532**](https://tools.ietf.org/html/rfc6532.html) \[https://tools.ietf.org/html/rfc6532.html\], as well as such MIME-related RFCs as [**RFC 2045**](https://tools.ietf.org/html/rfc2045.html) \[https://tools.ietf.org/html/rfc2045.html\], [**RFC 2046**](https://tools.ietf.org/html/rfc2046.html) \[https://tools.ietf.org/html/rfc2046.html\], [**RFC 2047**](https://tools.ietf.org/html/rfc2047.html) \[https://tools.ietf.org/html/rfc2047.html\], [**RFC 2183**](https://tools.ietf.org/html/rfc2183.html) \[https://tools.ietf.org/html/rfc2183.html\], and [**RFC 2231**](https://tools.ietf.org/html/rfc2231.html) \[https://tools.ietf.org/html/rfc2231.html\]. The overall structure of the email package can be divided into three major components, plus a fourth component that controls the behavior of the other components. The central component of the package is an "object model" that represents email messages. An application interacts with the package primarily through the object model interface defined in the [`message`](email.compat32-message.xhtml#module-email.message "email.message: The base class representing email messages in a fashion backward compatible with Python 3.2") sub-module. The application can use this API to ask questions about an existing email, to construct a new email, or to add or remove email subcomponents that themselves use the same object model interface. That is, following the nature of email messages and their MIME subcomponents, the email object model is a tree structure of objects that all provide the [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage")API. The other two major components of the package are the [`parser`](email.parser.xhtml#module-email.parser "email.parser: Parse flat text email messages to produce a message object structure.") and the [`generator`](email.generator.xhtml#module-email.generator "email.generator: Generate flat text email messages from a message structure."). The parser takes the serialized version of an email message (a stream of bytes) and converts it into a tree of [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage") objects. The generator takes an [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage") and turns it back into a serialized byte stream. (The parser and generator also handle streams of text characters, but this usage is discouraged as it is too easy to end up with messages that are not valid in one way or another.) The control component is the [`policy`](email.policy.xhtml#module-email.policy "email.policy: Controlling the parsing and generating of messages") module. Every [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage"), every [`generator`](email.generator.xhtml#module-email.generator "email.generator: Generate flat text email messages from a message structure."), and every [`parser`](email.parser.xhtml#module-email.parser "email.parser: Parse flat text email messages to produce a message object structure.") has an associated [`policy`](email.policy.xhtml#module-email.policy "email.policy: Controlling the parsing and generating of messages") object that controls its behavior. Usually an application only needs to specify the policy when an [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage") is created, either by directly instantiating an [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage") to create a new email, or by parsing an input stream using a [`parser`](email.parser.xhtml#module-email.parser "email.parser: Parse flat text email messages to produce a message object structure."). But the policy can be changed when the message is serialized using a [`generator`](email.generator.xhtml#module-email.generator "email.generator: Generate flat text email messages from a message structure."). This allows, for example, a generic email message to be parsed from disk, but to serialize it using standard SMTP settings when sending it to an email server. The email package does its best to hide the details of the various governing RFCs from the application. Conceptually the application should be able to treat the email message as a structured tree of unicode text and binary attachments, without having to worry about how these are represented when serialized. In practice, however, it is often necessary to be aware of at least some of the rules governing MIME messages and their structure, specifically the names and nature of the MIME "content types" and how they identify multipart documents. For the most part this knowledge should only be required for more complex applications, and even then it should only be the high level structure in question, and not the details of how those structures are represented. Since MIME content types are used widely in modern internet software (not just email), this will be a familiar concept to many programmers. The following sections describe the functionality of the [`email`](#module-email "email: Package supporting the parsing, manipulating, and generating email messages.") package. We start with the [`message`](email.compat32-message.xhtml#module-email.message "email.message: The base class representing email messages in a fashion backward compatible with Python 3.2") object model, which is the primary interface an application will use, and follow that with the [`parser`](email.parser.xhtml#module-email.parser "email.parser: Parse flat text email messages to produce a message object structure.") and [`generator`](email.generator.xhtml#module-email.generator "email.generator: Generate flat text email messages from a message structure.") components. Then we cover the [`policy`](email.policy.xhtml#module-email.policy "email.policy: Controlling the parsing and generating of messages") controls, which completes the treatment of the main components of the library. The next three sections cover the exceptions the package may raise and the defects (non-compliance with the RFCs) that the [`parser`](email.parser.xhtml#module-email.parser "email.parser: Parse flat text email messages to produce a message object structure.") may detect. Then we cover the [`headerregistry`](email.headerregistry.xhtml#module-email.headerregistry "email.headerregistry: Automatic Parsing of headers based on the field name") and the [`contentmanager`](email.contentmanager.xhtml#module-email.contentmanager "email.contentmanager: Storing and Retrieving Content from MIME Parts") sub-components, which provide tools for doing more detailed manipulation of headers and payloads, respectively. Both of these components contain features relevant to consuming and producing non-trivial messages, but also document their extensibility APIs, which will be of interest to advanced applications. Following those is a set of examples of using the fundamental parts of the APIs covered in the preceding sections. The foregoing represent the modern (unicode friendly) API of the email package. The remaining sections, starting with the [`Message`](email.compat32-message.xhtml#email.message.Message "email.message.Message")class, cover the legacy [`compat32`](email.policy.xhtml#email.policy.compat32 "email.policy.compat32") API that deals much more directly with the details of how email messages are represented. The [`compat32`](email.policy.xhtml#email.policy.compat32 "email.policy.compat32") API does *not* hide the details of the RFCs from the application, but for applications that need to operate at that level, they can be useful tools. This documentation is also relevant for applications that are still using the [`compat32`](email.policy.xhtml#email.policy.compat32 "email.policy.compat32") API for backward compatibility reasons. 在 3.6 版更改: Docs reorganized and rewritten to promote the new [`EmailMessage`](email.message.xhtml#email.message.EmailMessage "email.message.EmailMessage")/[`EmailPolicy`](email.policy.xhtml#email.policy.EmailPolicy "email.policy.EmailPolicy")API. Contents of the [`email`](#module-email "email: Package supporting the parsing, manipulating, and generating email messages.") package documentation: - [`email.message`: Representing an email message](email.message.xhtml) - [`email.parser`: Parsing email messages](email.parser.xhtml) - [FeedParser API](email.parser.xhtml#feedparser-api) - [Parser API](email.parser.xhtml#parser-api) - [Additional notes](email.parser.xhtml#additional-notes) - [`email.generator`: Generating MIME documents](email.generator.xhtml) - [`email.policy`: Policy Objects](email.policy.xhtml) - [`email.errors`: 异常和缺陷类](email.errors.xhtml) - [`email.headerregistry`: Custom Header Objects](email.headerregistry.xhtml) - [`email.contentmanager`: Managing MIME Content](email.contentmanager.xhtml) - [Content Manager Instances](email.contentmanager.xhtml#content-manager-instances) - [`email`: 示例](email.examples.xhtml) Legacy API: - [`email.message.Message`: Representing an email message using the `compat32` API](email.compat32-message.xhtml) - [`email.mime`: Creating email and MIME objects from scratch](email.mime.xhtml) - [`email.header`: Internationalized headers](email.header.xhtml) - [`email.charset`: Representing character sets](email.charset.xhtml) - [`email.encoders`: Encoders](email.encoders.xhtml) - [`email.utils`: 其他工具](email.utils.xhtml) - [`email.iterators`: Iterators](email.iterators.xhtml) 参见 Module [`smtplib`](smtplib.xhtml#module-smtplib "smtplib: SMTP protocol client (requires sockets).")SMTP (Simple Mail Transport Protocol) client Module [`poplib`](poplib.xhtml#module-poplib "poplib: POP3 protocol client (requires sockets).")POP (Post Office Protocol) client Module [`imaplib`](imaplib.xhtml#module-imaplib "imaplib: IMAP4 protocol client (requires sockets).")IMAP (Internet Message Access Protocol) client Module [`nntplib`](nntplib.xhtml#module-nntplib "nntplib: NNTP protocol client (requires sockets).")NNTP (Net News Transport Protocol) client Module [`mailbox`](mailbox.xhtml#module-mailbox "mailbox: Manipulate mailboxes in various formats")Tools for creating, reading, and managing collections of messages on disk using a variety standard formats. Module [`smtpd`](smtpd.xhtml#module-smtpd "smtpd: A SMTP server implementation in Python.")SMTP server framework (primarily useful for testing) ### 导航 - [索引](../genindex.xhtml "总目录") - [模块](../py-modindex.xhtml "Python 模块索引") | - [下一页](email.message.xhtml "email.message: Representing an email message") | - [上一页](netdata.xhtml "互联网数据处理") | -  - [Python](https://www.python.org/) » - zh\_CN 3.7.3 [文档](../index.xhtml) » - [Python 标准库](index.xhtml) » - [互联网数据处理](netdata.xhtml) » - $('.inline-search').show(0); | © [版权所有](../copyright.xhtml) 2001-2019, Python Software Foundation. Python 软件基金会是一个非盈利组织。 [请捐助。](https://www.python.org/psf/donations/) 最后更新于 5月 21, 2019. [发现了问题](../bugs.xhtml)？ 使用[Sphinx](http://sphinx.pocoo.org/)1.8.4 创建。