Searched full:email (Results 1 – 25 of 1478) sorted by relevance
12345678910>>...60
| /external/python/cpython3/Doc/library/ |
| D | email.rst | 1 :mod:`email` --- An email and MIME handling package
4 .. module:: email
6 email messages.
11 **Source code:** :source:`Lib/email/__init__.py`
15 The :mod:`email` package is a library for managing email messages. It is
16 specifically *not* designed to do any sending of email messages to SMTP
18 :mod:`smtplib` and :mod:`nntplib`. The :mod:`email` package attempts to be as
23 The overall structure of the email package can be divided into three major
27 The central component of the package is an "object model" that represents email
29 object model interface defined in the :mod:`~email.message` sub-module. The
[all …]
|
| D | email.mime.rst | 1 :mod:`email.mime`: Creating email and MIME objects from scratch
4 .. module:: email.mime
7 **Source code:** :source:`Lib/email/mime/`
11 This module is part of the legacy (``Compat32``) email API. Its functionality
12 is partially replaced by the :mod:`~email.contentmanager` in the new API, but
19 :class:`~email.message.Message` objects by hand. In fact, you can also take an
20 existing structure and add new :class:`~email.message.Message` objects, move them
24 You can create a new object structure by creating :class:`~email.message.Message`
26 messages though, the :mod:`email` package provides some convenient subclasses to
31 .. currentmodule:: email.mime.base
[all …]
|
| D | email.parser.rst | 1 :mod:`email.parser`: Parsing email messages
4 .. module:: email.parser
5 :synopsis: Parse flat text email messages to produce a message object structure.
7 **Source code:** :source:`Lib/email/parser.py`
12 created from whole cloth by creating an :class:`~email.message.EmailMessage`
14 using :meth:`~email.message.EmailMessage.set_content` and related methods, or
15 they can be created by parsing a serialized representation of the email
18 The :mod:`email` package provides a standard parser that understands most email
21 :class:`~email.message.EmailMessage` instance of the object structure. For
24 will return ``True`` from its :meth:`~email.message.EmailMessage.is_multipart`
[all …]
|
| D | email.policy.rst | 1 :mod:`email.policy`: Policy Objects
4 .. module:: email.policy
12 **Source code:** :source:`Lib/email/policy.py`
16 The :mod:`email` package's prime focus is the handling of email messages as
17 described by the various email and MIME RFCs. However, the general format of
18 email messages (a block of header fields each consisting of a name followed by
21 email. Some of these uses conform fairly closely to the main email RFCs, some
22 do not. Even when working with email, there are times when it is desirable to
24 interoperate with email servers that do not themselves follow the standards, or
28 Policy objects give the email package the flexibility to handle all these
[all …]
|
| D | email.generator.rst | 1 :mod:`email.generator`: Generating MIME documents
4 .. module:: email.generator
5 :synopsis: Generate flat text email messages from a message structure.
7 **Source code:** :source:`Lib/email/generator.py`
12 the email message represented by a message object structure. You will need to
18 As with the :mod:`email.parser` module, you aren't limited to the functionality
20 the bundled generator knows how to generate most email in a standards-compliant
21 way, should handle MIME and non-MIME email messages just fine, and is designed
23 assuming the same non-transforming :mod:`~email.policy` is used for both. That
25 :class:`~email.parser.BytesParser` class and then regenerating the serialized
[all …]
|
| D | email.header.rst | 1 :mod:`email.header`: Internationalized headers
4 .. module:: email.header
7 **Source code:** :source:`Lib/email/header.py`
11 This module is part of the legacy (``Compat32``) email API. In the current API
13 dictionary-like API of the :class:`~email.message.EmailMessage` class. In
19 :rfc:`2822` is the base standard that describes the format of email messages.
21 a time when most email was composed of ASCII characters only. :rfc:`2822` is a
22 specification written assuming email contains only 7-bit ASCII characters.
24 Of course, as email has been deployed worldwide, it has become
26 email messages. The base standard still requires email messages to be
[all …]
|
| D | email.errors.rst | 1 :mod:`email.errors`: Exception and Defect classes
4 .. module:: email.errors
5 :synopsis: The exception classes used by the email package.
7 **Source code:** :source:`Lib/email/errors.py`
11 The following exception classes are defined in the :mod:`email.errors` module:
16 This is the base class for all exceptions that the :mod:`email` package can
24 :class:`~email.parser.Parser` class. It is derived from
26 by :mod:`~email.headerregistry`.
33 :meth:`~email.message.EmailMessage.set_boundary` method will raise this
35 :class:`~email.header.Header` may raise this error for certain base64
[all …]
|
| D | email.compat32-message.rst | 3 :mod:`email.message.Message`: Representing an email message using the :data:`~email.policy.compat32…
6 .. module:: email.message
7 :synopsis: The base class representing email messages in a fashion
12 :class:`~email.message.EmailMessage` class, without the methods added by that
15 :class:`~email.message.EmailMessage` class, are not recommended unless you are
21 policy :attr:`~email.policy.Compat32`. If you are going to use another policy,
22 you should be using the :class:`~email.message.EmailMessage` class instead.
24 An email message consists of *headers* and a *payload*. Headers must be
56 If *policy* is specified (it must be an instance of a :mod:`~email.policy`
59 <email.policy.Compat32>` policy, which maintains backward compatibility with
[all …]
|
| D | email.examples.rst | 3 :mod:`email`: Examples
6 Here are a few examples of how to use the :mod:`email` package to read, write,
7 and send simple email messages, as well as more complex MIME messages.
12 .. literalinclude:: ../includes/email-simple.py
16 from the :mod:`~email.parser` module:
18 .. literalinclude:: ../includes/email-headers.py
24 .. literalinclude:: ../includes/email-mime.py
27 Here's an example of how to send the entire contents of a directory as an email
30 .. literalinclude:: ../includes/email-dir.py
36 .. literalinclude:: ../includes/email-unpack.py
[all …]
|
| D | email.message.rst | 1 :mod:`email.message`: Representing an email message
4 .. module:: email.message
5 :synopsis: The base class representing email messages.
10 **Source code:** :source:`Lib/email/message.py`
16 The central class in the :mod:`email` package is the :class:`EmailMessage`
17 class, imported from the :mod:`email.message` module. It is the base class for
18 the :mod:`email` object model. :class:`EmailMessage` provides the core
22 An email message consists of *headers* and a *payload* (which is also referred
57 :class:`~email.policy.default` policy, which follows the rules of the email
60 :mod:`~email.policy` documentation.
[all …]
|
| D | email.encoders.rst | 1 :mod:`email.encoders`: Encoders
4 .. module:: email.encoders
5 :synopsis: Encoders for email message payloads.
7 **Source code:** :source:`Lib/email/encoders.py`
11 This module is part of the legacy (``Compat32``) email API. In the
13 the :meth:`~email.message.EmailMessage.set_content` method.
17 When creating :class:`~email.message.Message` objects from scratch, you often
22 The :mod:`email` package provides some convenient encodings in its
24 :class:`~email.mime.audio.MIMEAudio` and :class:`~email.mime.image.MIMEImage`
|
| /external/python/cpython2/Doc/library/ |
| D | email.rst | 1 :mod:`email` --- An email and MIME handling package
4 .. module:: email
5 :synopsis: Package supporting the parsing, manipulating, and generating email messages,
14 The :mod:`email` package is a library for managing email messages, including
18 :mod:`mimecntl`. It is specifically *not* designed to do any sending of email
20 modules such as :mod:`smtplib` and :mod:`nntplib`. The :mod:`email` package
25 The primary distinguishing feature of the :mod:`email` package is that it splits
26 the parsing and generating of email messages from the internal *object model*
27 representation of email. Applications using the :mod:`email` package deal
36 The following sections describe the functionality of the :mod:`email` package.
[all …]
|
| D | email.mime.rst | 1 :mod:`email.mime`: Creating email and MIME objects from scratch
4 .. module:: email.mime
11 :class:`~email.message.Message` objects by hand. In fact, you can also take an
12 existing structure and add new :class:`~email.message.Message` objects, move them
16 You can create a new object structure by creating :class:`~email.message.Message`
18 messages though, the :mod:`email` package provides some convenient subclasses to
23 .. currentmodule:: email.mime.base
27 Module: :mod:`email.mime.base`
30 :class:`~email.message.Message`. Ordinarily you won't create instances
39 <email.message.Message.add_header>`.
[all …]
|
| D | email.parser.rst | 1 :mod:`email.parser`: Parsing email messages
4 .. module:: email.parser
5 :synopsis: Parse flat text email messages to produce a message object structure.
9 from whole cloth by instantiating :class:`~email.message.Message` objects and
10 stringing them together via :meth:`~email.message.Message.attach` and
11 :meth:`~email.message.Message.set_payload` calls, or they
12 can be created by parsing a flat text representation of the email message.
14 The :mod:`email` package provides a standard parser that understands most email
17 :class:`~email.message.Message` instance of the object structure. For simple,
20 return ``True`` from its :meth:`~email.message.Message.is_multipart` method, and
[all …]
|
| D | email.header.rst | 1 :mod:`email.header`: Internationalized headers
4 .. module:: email.header
8 :rfc:`2822` is the base standard that describes the format of email messages.
10 a time when most email was composed of ASCII characters only. :rfc:`2822` is a
11 specification written assuming email contains only 7-bit ASCII characters.
13 Of course, as email has been deployed worldwide, it has become
15 email messages. The base standard still requires email messages to be
17 written describing how to encode email containing non-ASCII characters into
19 :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports these standards
20 in its :mod:`email.header` and :mod:`email.charset` modules.
[all …]
|
| D | email.errors.rst | 1 :mod:`email.errors`: Exception and Defect classes
4 .. module:: email.errors
5 :synopsis: The exception classes used by the email package.
8 The following exception classes are defined in the :mod:`email.errors` module:
13 This is the base class for all exceptions that the :mod:`email` package can
20 This is the base class for exceptions raised by the :class:`~email.parser.Parser`
28 from the :meth:`Parser.parse <email.parser.Parser.parse>` or
29 :meth:`Parser.parsestr <email.parser.Parser.parsestr>` methods.
41 from the :meth:`Parser.parse <email.parser.Parser.parse>` or
42 :meth:`Parser.parsestr <email.parser.Parser.parsestr>` methods.
[all …]
|
| D | email-examples.rst | 3 :mod:`email`: Examples
6 Here are a few examples of how to use the :mod:`email` package to read, write,
7 and send simple email messages, as well as more complex MIME messages.
11 .. literalinclude:: ../includes/email-simple.py
17 .. literalinclude:: ../includes/email-headers.py
23 .. literalinclude:: ../includes/email-mime.py
26 Here's an example of how to send the entire contents of a directory as an email
29 .. literalinclude:: ../includes/email-dir.py
35 .. literalinclude:: ../includes/email-unpack.py
40 .. literalinclude:: ../includes/email-alternative.py
|
| D | email.charset.rst | 1 :mod:`email.charset`: Representing character sets
4 .. module:: email.charset
9 and character set conversions in email messages, as well as a character set
12 :mod:`email` package.
14 Import this class from the :mod:`email.charset` module.
21 Map character sets to their email properties.
23 This class provides information about the requirements imposed on email for a
27 character set in an email message in an RFC-compliant way.
30 in email headers or bodies. Certain character sets must be converted outright,
31 and are not allowed in email.
[all …]
|
| /external/python/cpython3/Lib/test/test_email/ |
| D | test_policy.py | 5 import email.policy
6 import email.parser
7 import email.generator
8 import email.message
9 from email import headerregistry
29 # These default values are the ones set on email.policy.default.
35 'header_factory': email.policy.EmailPolicy.header_factory,
37 'content_manager': email.policy.EmailPolicy.content_manager,
39 'message_factory': email.message.EmailMessage,
45 new_policy = email.policy.EmailPolicy()
[all …]
|
| /external/python/cpython2/Lib/email/ |
| D | __init__.py | 3 # Contact: email-sig@python.org
5 """A package for parsing, handling, and generating email messages."""
49 # of importing email since those cascadingly import most of the rest of the
50 # email package.
56 from email.parser import Parser
65 from email.parser import Parser
71 # email 4.0 module names), to old-style names (email 3.0 module names).
76 self.__name__ = 'email.' + module_name
86 # email.<old name> -> email.<new name is lowercased old name>
102 # email.MIME<old name> -> email.mime.<new name is lowercased old name>
[all …]
|
| D | charset.py | 3 # Contact: email-sig@python.org
13 import email.base64mime
14 import email.quoprimime
16 from email import errors
17 from email.encoders import encode_7or8bit
66 # them to the real ones used in email.
157 """Map character sets to their email properties.
159 This class provides information about the requirements imposed on email
163 information on how to use that character set in an email in an
167 when used in email headers or bodies. Certain character sets must be
[all …]
|
| /external/python/cpython3/Tools/scripts/ |
| D | mailerdaemon.py | 5 import email.message
15 class ErrorMessage(email.message.Message):
17 email.message.Message.__init__(self)
42 # If a re, it should contain at least a group (?P<email>...) which
43 # should refer to the email address. The re can also contain a group
49 # multiple email addresses. The second re is matched (not searched)
53 'error: (?P<reason>unresolvable): (?P<email>.+)',
55 '(?P<email>[^ \n].*)\n( .*\n)?'),
56 'remote execution.*\n.*rmail (?P<email>.+)',
58 ' +(?P<email>.*)\n(The following recipients did not receive your message:\n\n)?'),
[all …]
|
| /external/python/cpython2/Tools/scripts/ |
| D | mailerdaemon.py | 37 # If a re, it should contain at least a group (?P<email>...) which
38 # should refer to the email address. The re can also contain a group
44 # multiple email addresses. The second re is matched (not searched)
48 'error: (?P<reason>unresolvable): (?P<email>.+)',
50 '(?P<email>[^ \n].*)\n( .*\n)?'),
51 'remote execution.*\n.*rmail (?P<email>.+)',
53 ' +(?P<email>.*)\n(The following recipients did not receive your message:\n\n)?'),
54 '------- Failure Reasons --------\n\n(?P<reason>.*)\n(?P<email>.*)',
55 '^<(?P<email>.*)>:\n(?P<reason>.*)',
56 '^(?P<reason>User mailbox exceeds allowed size): (?P<email>.+)',
[all …]
|
| /external/javaparser/ |
| D | pom.xml | 41 <email>hexagonaal@gmail.com</email>
47 <email>jgesser@gmail.com</email>
51 <email>sebastian.kirsch@immobilienscout24.de</email>
62 <email>smiddypence@gmail.com</email>
68 <email>federico@tomassetti.me</email>
74 <email>ptitjes@free.fr</email>
82 <email>sebastian@topobyte.de</email>
87 <email>fly2best@gmail.com</email>
96 <email>morozov@altlinux.org</email>
101 <email>donny.nadolny@gmail.com</email>
[all …]
|
| /external/python/cpython3/Lib/email/ |
| D | architecture.rst | 1 :mod:`email` Package Architecture
7 The email package consists of three major components:
10 An object structure that represents an email message, and provides an
15 email message represented by those characters or bytes.
42 default :rfc:`5322` email message policy, we also have a policy that manages
51 The message model is implemented by the :class:`~email.message.Message` class.
103 :meth:`~email.policy.Policy.header_source_parse` method of the Policy. The
108 the :meth:`~email.policy.Policy.header_store_parse` method of the Policy, which
113 :meth:`~email.policy.Policy.header_fetch_parse` method of the Policy to
117 passed to the :meth:`~email.policy.Policy.fold` method of the Policy, which
[all …]
|
12345678910>>...60