Home
last modified time | relevance | path

Searched full:email (Results 1 – 25 of 1247) sorted by relevance

12345678910>>...50

/third_party/python/Doc/library/
Demail.rst1 :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 …]
Demail.mime.rst1 :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 …]
Demail.parser.rst1 :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 …]
Demail.policy.rst1 :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 …]
Demail.generator.rst1 :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 …]
Demail.header.rst1 :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 …]
Demail.errors.rst1 :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 …]
Demail.compat32-message.rst3 :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
13 :class:`~email.message.EmailMessage` class, without the methods added by that
16 :class:`~email.message.EmailMessage` class, are not recommended unless you are
22 policy :attr:`~email.policy.Compat32`. If you are going to use another policy,
23 you should be using the :class:`~email.message.EmailMessage` class instead.
25 An email message consists of *headers* and a *payload*. Headers must be
57 If *policy* is specified (it must be an instance of a :mod:`~email.policy`
60 <email.policy.Compat32>` policy, which maintains backward compatibility with
[all …]
Demail.examples.rst3 :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 …]
Demail.encoders.rst1 :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.
16 should not be called explicitly since the :class:`~email.mime.text.MIMEText`
22 When creating :class:`~email.message.Message` objects from scratch, you often
27 The :mod:`email` package provides some convenient encoders in its
29 :class:`~email.mime.audio.MIMEAudio` and :class:`~email.mime.image.MIMEImage`
Demail.charset.rst1 :mod:`email.charset`: Representing character sets
4 .. module:: email.charset
7 **Source code:** :source:`Lib/email/charset.py`
11 This module is part of the legacy (``Compat32``) email API. In the new
17 and character set conversions in email messages, as well as a character set
20 :mod:`email` package.
22 Import this class from the :mod:`email.charset` module.
27 Map character sets to their email properties.
29 This class provides information about the requirements imposed on email for a
33 character set in an email message in an RFC-compliant way.
[all …]
Demail.message.rst1 :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 …]
/third_party/node/deps/npm/test/fixtures/
Dlibnpmsearch-stream-result.js15 author: { name: 'Kat Marchán', email: 'kzm@zkat.tech' }, property
16 publisher: { username: 'isaacs', email: 'i@izs.me' }, property
18 { username: 'nlf', email: 'quitlahok@gmail.com' }, property
19 { username: 'ruyadorno', email: 'ruyadorno@hotmail.com' }, property
20 { username: 'darcyclarke', email: 'darcy@darcyclarke.me' }, property
21 { username: 'isaacs', email: 'i@izs.me' }, property
37 author: { name: 'Kat Marchán', email: 'kzm@sykosomatic.org' }, property
38 publisher: { username: 'nlf', email: 'quitlahok@gmail.com' }, property
40 { username: 'nlf', email: 'quitlahok@gmail.com' }, property
41 { username: 'ruyadorno', email: 'ruyadorno@hotmail.com' }, property
[all …]
/third_party/python/Lib/test/test_email/
Dtest_policy.py5 import email.errors
6 import email.policy
7 import email.parser
8 import email.generator
9 import email.message
10 from email import headerregistry
30 # These default values are the ones set on email.policy.default.
36 'header_factory': email.policy.EmailPolicy.header_factory,
38 'content_manager': email.policy.EmailPolicy.content_manager,
40 'message_factory': email.message.EmailMessage,
[all …]
/third_party/node/deps/npm/node_modules/socks-proxy-agent/
Dpackage.json11 "email": "nathan@tootallnate.net", string
18 "email": "josefrancisco.verdu@gmail.com" string
22 "email": "josh@joshglazebrook.com" string
26 "email": "talmobi@users.noreply.github.com" string
30 "email": "justin@indospace.io" string
34 "email": "github@jumoog.io" string
38 "email": "admin@hk1229.cn" string
42 "email": "matheus.frndes@gmail.com" string
46 "email": "richardkazuomiller@gmail.com" string
50 "email": "shantanu34@outlook.com" string
[all …]
/third_party/python/Tools/scripts/
Dmailerdaemon.py5 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 …]
/third_party/libwebsockets/minimal-examples/api-tests/api-test-smtp_client/
Dmain.c19 email_sent_or_failed(struct lws_smtp_email *email, void *buf, size_t len) in email_sent_or_failed() argument
21 free(email); in email_sent_or_failed()
28 * the test. In our case, we need to queue up a test email to send on the
35 lws_smtp_email_t *email = (lws_smtp_email_t *) in smtp_test_instance_init() local
36 malloc(sizeof(*email) + 2048); in smtp_test_instance_init()
38 if (!email) in smtp_test_instance_init()
41 /* attach an email to it */ in smtp_test_instance_init()
43 memset(email, 0, sizeof(*email)); in smtp_test_instance_init()
44 email->data = NULL /* email specific user data */; in smtp_test_instance_init()
45 email->email_from = "noreply@warmcat.com"; in smtp_test_instance_init()
[all …]
/third_party/ffmpeg/doc/
Dmailing-list-faq.texi19 subscribes to the list. It is somewhat like a forum but in email form.
51 send an email:
55 Email @email{ffmpeg-user@@ffmpeg.org} to send a message to the
59 Email @email{libav-user@@ffmpeg.org} to send a message to the
63 Email @email{ffmpeg-devel@@ffmpeg.org} to send a message to the
72 Email @email{ffmpeg-user-request@@ffmpeg.org} with the subject
82 Email @email{ffmpeg-user-request@@ffmpeg.org} with subject @emph{unsubscribe}.
85 scroll to bottom of page, enter your email address in the box, and click
124 You should have received an email with the subject @emph{Your message to <mailing list name> awaits…
141 Click the email link at the top of the message just under the subject
[all …]
/third_party/node/deps/npm/test/lib/commands/
Dadduser.js47 stdin: ['test-user', 'test-password', 'test-email@npmjs.org'],
53 '//registry.npmjs.org/:email=test-email-old@npmjs.org',
60 email: 'test-email@npmjs.org', property
64 t.same(npm.config.get('email'), 'test-email-old@npmjs.org')
68 email: 'test-email-old@npmjs.org', property
69 }, 'should only have token and un-nerfed old email')
74 stdin: ['test-user', 'test-password', 'test-email@npmjs.org'],
83 email: 'test-email@npmjs.org', property
97 stdin: ['test-user', 'test-password', 'test-email@npmjs.org'],
110 email: 'test-email@npmjs.org', property
[all …]
/third_party/libwebsockets/include/libwebsockets/abstract/protocols/
Dsmtp.h29 * These apis let you communicate with a local SMTP server to send email from
33 * 25 and able to send email using the "mail" commandline app. Usually distro
38 * connections, and provides and email queue and retry management.
78 * lws_smtpc_add_email() - Allocates and queues an email object
81 * \param payload: the email payload string, with headers and terminating .
83 * \param sender: the sender name and email
84 * \param recipient: the recipient name and email
86 * \param done: callback called when the email send succeeded or failed
88 * Allocates an email object and copies the payload, sender and recipient into
89 * it and initializes it. Returns NULL if OOM, otherwise the allocated email
[all …]
/third_party/typescript/tests/cases/user/formik/
Dindex.tsx5 type MyData = {email: string, password: string};
27 email: '',
33 if (!values.email) {
34 errors.email = 'Required';
36 !/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i.test(values.email)
38 errors.email = 'Invalid email address';
70 type="email"
71 name="email"
74 value={values.email}
76 {touched.email && errors.email && <div>{errors.email}</div>}
/third_party/python/Lib/email/
Darchitecture.rst1 :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 …]
/third_party/node/deps/npm/test/lib/utils/
Dread-user-info.js19 email: (email) => {
20 if (email.startsWith('invalid')) {
21 return new Error('invalid email')
94 t.test('email', async (t) => {
100 const result = await readUserInfo.email()
101 t.equal(result, 'foo@bar.baz', 'received the email')
104 t.test('email - invalid warns and retries', async (t) => {
111 const pResult = readUserInfo.email(null, null)
114 t.equal(result, 'foo@bar.baz', 'received the email')
115 t.equal(logMsg, 'invalid email')
/third_party/node/deps/npm/node_modules/npm-user-validate/lib/
Dindex.js1 exports.email = email
13 email: {
14 length: 'Email length must be less then or equal to 254 characters long',
15 valid: 'Email must be an email address',
48 function email (em) { function
50 return new Error(requirements.email.length)
53 return new Error(requirements.email.valid)
/third_party/typescript/tests/baselines/reference/
DcomplicatedIndexedAccessKeyofReliesOnKeyofNeverUpperBound.errors.txt5 …Type '"text" | "email"' is not assignable to type 'ChannelOfType<T, TextChannel>["type"] & Channel…
9 … Type '"text" | "email"' is not assignable to type 'ChannelOfType<T, TextChannel>["type"]'.
13 Type '"text" | "email"' is not assignable to type 'T & "text"'.
16 … type 'T', but 'T' could be instantiated with a different subtype of constraint '"text" | "email"'.
18 Type '"text" | "email"' is not assignable to type '"text"'.
19 Type '"email"' is not assignable to type '"text"'.
31 type: 'email';
61 !!! error TS2322: Type '"text" | "email"' is not assignable to type 'ChannelOfType<T, TextC…
65 !!! error TS2322: Type '"text" | "email"' is not assignable to type 'ChannelOfType<…
69 !!! error TS2322: Type '"text" | "email"' is not assignable to type 'T & "t…
[all …]

12345678910>>...50