mirror of
https://github.com/python/cpython.git
synced 2025-10-17 20:28:43 +00:00

* gh-55454: Add IMAP4 IDLE support to imaplib This extends imaplib with support for the rfc2177 IMAP IDLE command, as requested in #55454. It allows events to be pushed to a client as they occur, rather than having to continually poll for mailbox changes. The interface is a new idle() method, which returns an iterable context manager. Entering the context starts IDLE mode, during which events (untagged responses) can be retrieved using the iteration protocol. Exiting the context sends DONE to the server, ending IDLE mode. An optional time limit for the IDLE session is supported, for use with servers that impose an inactivity timeout. The context manager also offers a burst() method, designed for programs wishing to process events in batch rather than one at a time. Notable differences from other implementations: - It's an extension to imaplib, rather than a replacement. - It doesn't introduce additional threads. - It doesn't impose new requirements on the use of imaplib's existing methods. - It passes the unit tests in CPython's test/test_imaplib.py module (and adds new ones). - It works on Windows, Linux, and other unix-like systems. - It makes IDLE available on all of imaplib's client variants (including IMAP4_stream). - The interface is pythonic and easy to use. Caveats: - Due to a Windows limitation, the special case of IMAP4_stream running on Windows lacks a duration/timeout feature. (This is the stdin/stdout pipe connection variant; timeouts work fine for socket-based connections, even on Windows.) I have documented it where appropriate. - The file-like imaplib instance attributes are changed from buffered to unbuffered mode. This could potentially break any client code that uses those objects directly without expecting partial reads/writes. However, these attributes are undocumented. As such, I think (and PEP 8 confirms) that they are fair game for changes. https://peps.python.org/pep-0008/#public-and-internal-interfaces Usage examples: https://github.com/python/cpython/issues/55454#issuecomment-2227543041 Original discussion: https://discuss.python.org/t/gauging-interest-in-my-imap4-idle-implementation-for-imaplib/59272 Earlier requests and suggestions: https://github.com/python/cpython/issues/55454 https://mail.python.org/archives/list/python-ideas@python.org/thread/C4TVEYL5IBESQQPPS5GBR7WFBXCLQMZ2/ * gh-55454: Clarify imaplib idle() docs - Add example idle response tuples, to make the minor difference from other imaplib response tuples more obvious. - Merge the idle context manager's burst() method docs with the IMAP object's idle() method docs, for easier understanding. - Upgrade the Windows note regarding lack of pipe timeouts to a warning. - Rephrase various things for clarity. * docs: words instead of <= Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * docs: improve style in an example Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * docs: grammatical edit Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * docs consistency Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * comment -> docstring Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * docs: refer to imaplib as "this module" Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * imaplib: simplify & clarify idle debug message Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * imaplib: elaborate in idle context manager comment * imaplib: re-raise BaseException instead of bare except Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * imaplib: convert private doc string to comment * docs: correct mistake in imaplib example This is a correction to8077f2eab2
, which changed a variable name in only one place and broke the subsequent reference to it, departed from the naming convention used in the rest of the module, and shadowed the type() builtin along the way. * imaplib: simplify example code in doc string This is for consistency with the documentation change in8077f2eab2
and subsequent correction in013bbf18fc
. * imaplib: rename _Idler to Idler, update its docs * imaplib: add comment in Idler._pop() Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * imaplib: remove unnecessary blank line Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * imaplib: comment on use of unbuffered pipes * docs: imaplib: use the reStructuredText :class: role Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * Revert "docs: imaplib: use the reStructuredText :class: role" This reverts commitf385e441df
, because it triggers CI failures in the docs by referencing a class that is (deliberately) undocumented. * docs: imaplib: use the reST :class: role, escaped This is a different approach tof385e441df
, which was reverted for creating dangling link references. By prefixing the reStructuredText role target with a ! we disable conversion to a link, thereby passing continuous integration checks even though the referenced class is deliberately absent from the documentation. * docs: refer to IMAP4 IDLE instead of just IDLE This clarifies that we are referring to the email protocol, not the editor with the same name. Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> * imaplib: IDLE -> IMAP4 IDLE in exception message Co-authored-by: Peter Bierma <zintensitydev@gmail.com> * docs: imaplib idle() phrasing and linking tweaks * docs: imaplib: avoid linking to an invalid target This reverts and rephrases part ofa3f21cd75b
which created links to a method on a deliberately undocumented class. The links didn't work consistently, and caused sphinx warnings that broke cpython's continuous integration tests. * imaplib: update test after recent exception change This fixes a test that was broken by changing an exception inb01de95171
* imaplib: rename idle() dur argument to duration * imaplib: bytes.index() -> bytes.find() This makes it more obvious which statement triggers the branch. * imaplib: remove no-longer-necessary statement Co-authored-by: Martin Panter <vadmium@users.noreply.github.com> * docs: imaplib: concise & valid method links The burst() method is a little tricky to link in restructuredText, due to quirks of its parent class. This syntax allows sphinx to generate working links without generating warnings (which break continuous integration) and without burdening the reader with unimportant namespace qualifications. It makes the reST source ugly, but few people read the reST source, so it's a tolerable tradeoff. * imaplib: note data types present in IDLE responses * docs: imaplib: add comma to reST changes header Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com> * imaplib: sync doc strings with reST docs * docs: imaplib: minor Idler clarifications * imaplib: idle: emit (type, [data, ...]) tuples This allows our iterator to emit untagged responses that contain literal strings in the same way that imaplib's existing methods do, while still emitting exactly one whole response per iteration. * imaplib: while/yield instead of yield from iter() * imaplib: idle: use deadline idiom when iterating This simplifies the code, and avoids idle duration drift from time spent processing each iteration. * docs: imaplib: state duration/interval arg types * docs: imaplib: minor rephrasing of a sentence * docs: imaplib: reposition a paragraph This might improve readability, especially when encountering Idler.burst() for the first time. * docs: imaplib: wrap long lines in idle() section * docs: imaplib: note: Idler objects require 'with' * docs: imaplib: say that 29 minutes is 1740 seconds * docs: imaplib: mark a paragraph as a 'tip' * docs: imaplib: rephrase reference to MS Windows * imaplib: end doc string titles with a period * imaplib: idle: socket timeouts instead of select() IDLE timeouts were originally implemented using select() after checking for the presence of already-buffered data. That allowed timeouts on pipe connetions like IMAP4_stream. However, it seemed possible that SSL data arriving without any IMAP data afterward could cause select() to indicate available application data when there was none, leading to a read() call that would block with no timeout. It was unclear under what conditions this would happen in practice. This change switches to socket timeouts instead of select(), just to be safe. This also reverts IMAP4_stream changes that were made to support IDLE timeouts, since our new implementation only supports socket connections. * imaplib: Idler: rename private state attributes * imaplib: rephrase a comment in example code * docs: imaplib: idle: use Sphinx code-block:: pycon * docs: whatsnew: imaplib: reformat IMAP4.idle entry * imaplib: idle: make doc strings brief Since we generally rely on the reST/html documentation for details, we can keep these doc strings short. This matches the module's existing doc string style and avoids having to sync small changes between two files. * imaplib: Idler: split assert into two statements * imaplib: Idler: move assignment out of try: block * imaplib: Idler: move __exit__() for readability * imaplib: Idler: move __next__() for readability * imaplib: test: make IdleCmdHandler a global class * docs: imaplib: idle: collapse double-spaces * imaplib: warn on use of undocumented 'file' attr * imaplib: revert import reformatting Since we no longer import platform or selectors, the original import statement style can be restored, reducing the footprint of PR #122542. * imaplib: restore original exception msg formatting This reduces the footprint of PR #122542. * docs: imaplib: idle: versionadded:: next * imaplib: move import statement to where it's used This import is only needed if external code tries to use an attribute that it shouldn't be using. Making it a local import reduces module loading time in supported cases. * imaplib test: RuntimeWarning on IMAP4.file access * imaplib: use stacklevel=2 in warnings.warn() * imaplib test: simplify IMAP4.file warning test * imaplib test: pre-idle-continuation response * imaplib test: post-done untagged response * imaplib: downgrade idle-denied exception to error This makes it easier for client code to distinguish a temporary rejection of the IDLE command from a server responding incorrectly to IDLE. * imaplib: simplify check for socket object * imaplib: narrow the scope of IDLE socket timeouts If an IDLE duration or burst() was in use, and an unsolicited response contained a literal string, and crossed a packet boundary, and the subsequent packet was delayed beyond the IDLE feature's time limit, the timeout would leave the incoming protocol stream in a bad state (with the tail of that response appearing where the start of a response is expected). This change moves the IDLE socket timeout to cover only the start of a response, so it can no longer cause that problem. * imaplib: preserve partial reads on exception This ensures that short IDLE durations / burst() intervals won't risk corrupting response lines that span multiple packets. * imaplib: read/readline: save multipart buffer tail For resilience if read() or readline() ever complete with more than one bytes object remaining in the buffer. This is not expected to happen, but it seems wise to be prepared for a future change making it possible. * imaplib: use TimeoutError subclass only if needed * doc: imaplib: elaborate on IDLE response delivery * doc: imaplib: elaborate in note re: IMAP4.response * imaplib: comment on benefit of reading in chunks Our read() implementation designed to support IDLE replaces the one from PR #119514, fixing the same problem it was addressing. The tests that it added are preserved. * imaplib: readline(): treat ConnectionError as EOF --------- Co-authored-by: Gregory P. Smith <greg@krypto.org> Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Guido van Rossum <guido@python.org> Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Martin Panter <vadmium@users.noreply.github.com> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
722 lines
24 KiB
ReStructuredText
722 lines
24 KiB
ReStructuredText
:mod:`!imaplib` --- IMAP4 protocol client
|
|
=========================================
|
|
|
|
.. module:: imaplib
|
|
:synopsis: IMAP4 protocol client (requires sockets).
|
|
|
|
.. moduleauthor:: Piers Lauder <piers@communitysolutions.com.au>
|
|
.. sectionauthor:: Piers Lauder <piers@communitysolutions.com.au>
|
|
.. revised by ESR, January 2000
|
|
.. changes for IMAP4_SSL by Tino Lange <Tino.Lange@isg.de>, March 2002
|
|
.. changes for IMAP4_stream by Piers Lauder <piers@communitysolutions.com.au>,
|
|
November 2002
|
|
.. changes for IMAP4 IDLE by Forest <forestix@nom.one>, August 2024
|
|
|
|
**Source code:** :source:`Lib/imaplib.py`
|
|
|
|
.. index::
|
|
pair: IMAP4; protocol
|
|
pair: IMAP4_SSL; protocol
|
|
pair: IMAP4_stream; protocol
|
|
|
|
--------------
|
|
|
|
This module defines three classes, :class:`IMAP4`, :class:`IMAP4_SSL` and
|
|
:class:`IMAP4_stream`, which encapsulate a connection to an IMAP4 server and
|
|
implement a large subset of the IMAP4rev1 client protocol as defined in
|
|
:rfc:`2060`. It is backward compatible with IMAP4 (:rfc:`1730`) servers, but
|
|
note that the ``STATUS`` command is not supported in IMAP4.
|
|
|
|
.. include:: ../includes/wasm-notavail.rst
|
|
|
|
Three classes are provided by the :mod:`imaplib` module, :class:`IMAP4` is the
|
|
base class:
|
|
|
|
|
|
.. class:: IMAP4(host='', port=IMAP4_PORT, timeout=None)
|
|
|
|
This class implements the actual IMAP4 protocol. The connection is created and
|
|
protocol version (IMAP4 or IMAP4rev1) is determined when the instance is
|
|
initialized. If *host* is not specified, ``''`` (the local host) is used. If
|
|
*port* is omitted, the standard IMAP4 port (143) is used. The optional *timeout*
|
|
parameter specifies a timeout in seconds for the connection attempt.
|
|
If timeout is not given or is ``None``, the global default socket timeout is used.
|
|
|
|
The :class:`IMAP4` class supports the :keyword:`with` statement. When used
|
|
like this, the IMAP4 ``LOGOUT`` command is issued automatically when the
|
|
:keyword:`!with` statement exits. E.g.::
|
|
|
|
>>> from imaplib import IMAP4
|
|
>>> with IMAP4("domain.org") as M:
|
|
... M.noop()
|
|
...
|
|
('OK', [b'Nothing Accomplished. d25if65hy903weo.87'])
|
|
|
|
.. versionchanged:: 3.5
|
|
Support for the :keyword:`with` statement was added.
|
|
|
|
.. versionchanged:: 3.9
|
|
The optional *timeout* parameter was added.
|
|
|
|
Three exceptions are defined as attributes of the :class:`IMAP4` class:
|
|
|
|
|
|
.. exception:: IMAP4.error
|
|
|
|
Exception raised on any errors. The reason for the exception is passed to the
|
|
constructor as a string.
|
|
|
|
|
|
.. exception:: IMAP4.abort
|
|
|
|
IMAP4 server errors cause this exception to be raised. This is a sub-class of
|
|
:exc:`IMAP4.error`. Note that closing the instance and instantiating a new one
|
|
will usually allow recovery from this exception.
|
|
|
|
|
|
.. exception:: IMAP4.readonly
|
|
|
|
This exception is raised when a writable mailbox has its status changed by the
|
|
server. This is a sub-class of :exc:`IMAP4.error`. Some other client now has
|
|
write permission, and the mailbox will need to be re-opened to re-obtain write
|
|
permission.
|
|
|
|
|
|
There's also a subclass for secure connections:
|
|
|
|
|
|
.. class:: IMAP4_SSL(host='', port=IMAP4_SSL_PORT, *, ssl_context=None, \
|
|
timeout=None)
|
|
|
|
This is a subclass derived from :class:`IMAP4` that connects over an SSL
|
|
encrypted socket (to use this class you need a socket module that was compiled
|
|
with SSL support). If *host* is not specified, ``''`` (the local host) is used.
|
|
If *port* is omitted, the standard IMAP4-over-SSL port (993) is used.
|
|
*ssl_context* is a :class:`ssl.SSLContext` object which allows bundling
|
|
SSL configuration options, certificates and private keys into a single
|
|
(potentially long-lived) structure. Please read :ref:`ssl-security` for
|
|
best practices.
|
|
|
|
The optional *timeout* parameter specifies a timeout in seconds for the
|
|
connection attempt. If timeout is not given or is ``None``, the global default
|
|
socket timeout is used.
|
|
|
|
.. versionchanged:: 3.3
|
|
*ssl_context* parameter was added.
|
|
|
|
.. versionchanged:: 3.4
|
|
The class now supports hostname check with
|
|
:attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* (see
|
|
:const:`ssl.HAS_SNI`).
|
|
|
|
.. versionchanged:: 3.9
|
|
The optional *timeout* parameter was added.
|
|
|
|
.. versionchanged:: 3.12
|
|
The deprecated *keyfile* and *certfile* parameters have been removed.
|
|
|
|
The second subclass allows for connections created by a child process:
|
|
|
|
|
|
.. class:: IMAP4_stream(command)
|
|
|
|
This is a subclass derived from :class:`IMAP4` that connects to the
|
|
``stdin/stdout`` file descriptors created by passing *command* to
|
|
``subprocess.Popen()``.
|
|
|
|
|
|
The following utility functions are defined:
|
|
|
|
|
|
.. function:: Internaldate2tuple(datestr)
|
|
|
|
Parse an IMAP4 ``INTERNALDATE`` string and return corresponding local
|
|
time. The return value is a :class:`time.struct_time` tuple or
|
|
``None`` if the string has wrong format.
|
|
|
|
.. function:: Int2AP(num)
|
|
|
|
Converts an integer into a bytes representation using characters from the set
|
|
[``A`` .. ``P``].
|
|
|
|
|
|
.. function:: ParseFlags(flagstr)
|
|
|
|
Converts an IMAP4 ``FLAGS`` response to a tuple of individual flags.
|
|
|
|
|
|
.. function:: Time2Internaldate(date_time)
|
|
|
|
Convert *date_time* to an IMAP4 ``INTERNALDATE`` representation.
|
|
The return value is a string in the form: ``"DD-Mmm-YYYY HH:MM:SS
|
|
+HHMM"`` (including double-quotes). The *date_time* argument can
|
|
be a number (int or float) representing seconds since epoch (as
|
|
returned by :func:`time.time`), a 9-tuple representing local time
|
|
an instance of :class:`time.struct_time` (as returned by
|
|
:func:`time.localtime`), an aware instance of
|
|
:class:`datetime.datetime`, or a double-quoted string. In the last
|
|
case, it is assumed to already be in the correct format.
|
|
|
|
Note that IMAP4 message numbers change as the mailbox changes; in particular,
|
|
after an ``EXPUNGE`` command performs deletions the remaining messages are
|
|
renumbered. So it is highly advisable to use UIDs instead, with the UID command.
|
|
|
|
At the end of the module, there is a test section that contains a more extensive
|
|
example of usage.
|
|
|
|
|
|
.. seealso::
|
|
|
|
Documents describing the protocol, sources for servers
|
|
implementing it, by the University of Washington's IMAP Information Center
|
|
can all be found at (**Source Code**) https://github.com/uw-imap/imap (**Not Maintained**).
|
|
|
|
|
|
.. _imap4-objects:
|
|
|
|
IMAP4 Objects
|
|
-------------
|
|
|
|
All IMAP4rev1 commands are represented by methods of the same name, either
|
|
uppercase or lowercase.
|
|
|
|
All arguments to commands are converted to strings, except for ``AUTHENTICATE``,
|
|
and the last argument to ``APPEND`` which is passed as an IMAP4 literal. If
|
|
necessary (the string contains IMAP4 protocol-sensitive characters and isn't
|
|
enclosed with either parentheses or double quotes) each string is quoted.
|
|
However, the *password* argument to the ``LOGIN`` command is always quoted. If
|
|
you want to avoid having an argument string quoted (eg: the *flags* argument to
|
|
``STORE``) then enclose the string in parentheses (eg: ``r'(\Deleted)'``).
|
|
|
|
Most commands return a tuple: ``(type, [data, ...])`` where *type* is usually
|
|
``'OK'`` or ``'NO'``, and *data* is either the text from the command response,
|
|
or mandated results from the command. Each *data* is either a ``bytes``, or a
|
|
tuple. If a tuple, then the first part is the header of the response, and the
|
|
second part contains the data (ie: 'literal' value).
|
|
|
|
The *message_set* options to commands below is a string specifying one or more
|
|
messages to be acted upon. It may be a simple message number (``'1'``), a range
|
|
of message numbers (``'2:4'``), or a group of non-contiguous ranges separated by
|
|
commas (``'1:3,6:9'``). A range can contain an asterisk to indicate an infinite
|
|
upper bound (``'3:*'``).
|
|
|
|
An :class:`IMAP4` instance has the following methods:
|
|
|
|
|
|
.. method:: IMAP4.append(mailbox, flags, date_time, message)
|
|
|
|
Append *message* to named mailbox.
|
|
|
|
|
|
.. method:: IMAP4.authenticate(mechanism, authobject)
|
|
|
|
Authenticate command --- requires response processing.
|
|
|
|
*mechanism* specifies which authentication mechanism is to be used - it should
|
|
appear in the instance variable ``capabilities`` in the form ``AUTH=mechanism``.
|
|
|
|
*authobject* must be a callable object::
|
|
|
|
data = authobject(response)
|
|
|
|
It will be called to process server continuation responses; the *response*
|
|
argument it is passed will be ``bytes``. It should return ``bytes`` *data*
|
|
that will be base64 encoded and sent to the server. It should return
|
|
``None`` if the client abort response ``*`` should be sent instead.
|
|
|
|
.. versionchanged:: 3.5
|
|
string usernames and passwords are now encoded to ``utf-8`` instead of
|
|
being limited to ASCII.
|
|
|
|
|
|
.. method:: IMAP4.check()
|
|
|
|
Checkpoint mailbox on server.
|
|
|
|
|
|
.. method:: IMAP4.close()
|
|
|
|
Close currently selected mailbox. Deleted messages are removed from writable
|
|
mailbox. This is the recommended command before ``LOGOUT``.
|
|
|
|
|
|
.. method:: IMAP4.copy(message_set, new_mailbox)
|
|
|
|
Copy *message_set* messages onto end of *new_mailbox*.
|
|
|
|
|
|
.. method:: IMAP4.create(mailbox)
|
|
|
|
Create new mailbox named *mailbox*.
|
|
|
|
|
|
.. method:: IMAP4.delete(mailbox)
|
|
|
|
Delete old mailbox named *mailbox*.
|
|
|
|
|
|
.. method:: IMAP4.deleteacl(mailbox, who)
|
|
|
|
Delete the ACLs (remove any rights) set for who on mailbox.
|
|
|
|
|
|
.. method:: IMAP4.enable(capability)
|
|
|
|
Enable *capability* (see :rfc:`5161`). Most capabilities do not need to be
|
|
enabled. Currently only the ``UTF8=ACCEPT`` capability is supported
|
|
(see :RFC:`6855`).
|
|
|
|
.. versionadded:: 3.5
|
|
The :meth:`enable` method itself, and :RFC:`6855` support.
|
|
|
|
|
|
.. method:: IMAP4.expunge()
|
|
|
|
Permanently remove deleted items from selected mailbox. Generates an ``EXPUNGE``
|
|
response for each deleted message. Returned data contains a list of ``EXPUNGE``
|
|
message numbers in order received.
|
|
|
|
|
|
.. method:: IMAP4.fetch(message_set, message_parts)
|
|
|
|
Fetch (parts of) messages. *message_parts* should be a string of message part
|
|
names enclosed within parentheses, eg: ``"(UID BODY[TEXT])"``. Returned data
|
|
are tuples of message part envelope and data.
|
|
|
|
|
|
.. method:: IMAP4.getacl(mailbox)
|
|
|
|
Get the ``ACL``\ s for *mailbox*. The method is non-standard, but is supported
|
|
by the ``Cyrus`` server.
|
|
|
|
|
|
.. method:: IMAP4.getannotation(mailbox, entry, attribute)
|
|
|
|
Retrieve the specified ``ANNOTATION``\ s for *mailbox*. The method is
|
|
non-standard, but is supported by the ``Cyrus`` server.
|
|
|
|
|
|
.. method:: IMAP4.getquota(root)
|
|
|
|
Get the ``quota`` *root*'s resource usage and limits. This method is part of the
|
|
IMAP4 QUOTA extension defined in rfc2087.
|
|
|
|
|
|
.. method:: IMAP4.getquotaroot(mailbox)
|
|
|
|
Get the list of ``quota`` ``roots`` for the named *mailbox*. This method is part
|
|
of the IMAP4 QUOTA extension defined in rfc2087.
|
|
|
|
|
|
.. method:: IMAP4.idle(duration=None)
|
|
|
|
Return an :class:`!Idler`: an iterable context manager implementing the
|
|
IMAP4 ``IDLE`` command as defined in :rfc:`2177`.
|
|
|
|
The returned object sends the ``IDLE`` command when activated by the
|
|
:keyword:`with` statement, produces IMAP untagged responses via the
|
|
:term:`iterator` protocol, and sends ``DONE`` upon context exit.
|
|
|
|
All untagged responses that arrive after sending the ``IDLE`` command
|
|
(including any that arrive before the server acknowledges the command) will
|
|
be available via iteration. Any leftover responses (those not iterated in
|
|
the :keyword:`with` context) can be retrieved in the usual way after
|
|
``IDLE`` ends, using :meth:`IMAP4.response`.
|
|
|
|
Responses are represented as ``(type, [data, ...])`` tuples, as described
|
|
in :ref:`IMAP4 Objects <imap4-objects>`.
|
|
|
|
The *duration* argument sets a maximum duration (in seconds) to keep idling,
|
|
after which any ongoing iteration will stop. It can be an :class:`int` or
|
|
:class:`float`, or ``None`` for no time limit.
|
|
Callers wishing to avoid inactivity timeouts on servers that impose them
|
|
should keep this at most 29 minutes (1740 seconds).
|
|
Requires a socket connection; *duration* must be ``None`` on
|
|
:class:`IMAP4_stream` connections.
|
|
|
|
.. code-block:: pycon
|
|
|
|
>>> with M.idle(duration=29 * 60) as idler:
|
|
... for typ, data in idler:
|
|
... print(typ, data)
|
|
...
|
|
EXISTS [b'1']
|
|
RECENT [b'1']
|
|
|
|
|
|
.. method:: Idler.burst(interval=0.1)
|
|
|
|
Yield a burst of responses no more than *interval* seconds apart
|
|
(expressed as an :class:`int` or :class:`float`).
|
|
|
|
This :term:`generator` is an alternative to iterating one response at a
|
|
time, intended to aid in efficient batch processing. It retrieves the
|
|
next response along with any immediately available subsequent responses.
|
|
(For example, a rapid series of ``EXPUNGE`` responses after a bulk
|
|
delete.)
|
|
|
|
Requires a socket connection; does not work on :class:`IMAP4_stream`
|
|
connections.
|
|
|
|
.. code-block:: pycon
|
|
|
|
>>> with M.idle() as idler:
|
|
... # get a response and any others following by < 0.1 seconds
|
|
... batch = list(idler.burst())
|
|
... print(f'processing {len(batch)} responses...')
|
|
... print(batch)
|
|
...
|
|
processing 3 responses...
|
|
[('EXPUNGE', [b'2']), ('EXPUNGE', [b'1']), ('RECENT', [b'0'])]
|
|
|
|
.. tip::
|
|
|
|
The ``IDLE`` context's maximum duration, as passed to
|
|
:meth:`IMAP4.idle`, is respected when waiting for the first response
|
|
in a burst. Therefore, an expired :class:`!Idler` will cause this
|
|
generator to return immediately without producing anything. Callers
|
|
should consider this if using it in a loop.
|
|
|
|
|
|
.. note::
|
|
|
|
The iterator returned by :meth:`IMAP4.idle` is usable only within a
|
|
:keyword:`with` statement. Before or after that context, unsolicited
|
|
responses are collected internally whenever a command finishes, and can
|
|
be retrieved with :meth:`IMAP4.response`.
|
|
|
|
.. note::
|
|
|
|
The :class:`!Idler` class name and structure are internal interfaces,
|
|
subject to change. Calling code can rely on its context management,
|
|
iteration, and public method to remain stable, but should not subclass,
|
|
instantiate, compare, or otherwise directly reference the class.
|
|
|
|
.. versionadded:: next
|
|
|
|
|
|
.. method:: IMAP4.list([directory[, pattern]])
|
|
|
|
List mailbox names in *directory* matching *pattern*. *directory* defaults to
|
|
the top-level mail folder, and *pattern* defaults to match anything. Returned
|
|
data contains a list of ``LIST`` responses.
|
|
|
|
|
|
.. method:: IMAP4.login(user, password)
|
|
|
|
Identify the client using a plaintext password. The *password* will be quoted.
|
|
|
|
|
|
.. method:: IMAP4.login_cram_md5(user, password)
|
|
|
|
Force use of ``CRAM-MD5`` authentication when identifying the client to protect
|
|
the password. Will only work if the server ``CAPABILITY`` response includes the
|
|
phrase ``AUTH=CRAM-MD5``.
|
|
|
|
|
|
.. method:: IMAP4.logout()
|
|
|
|
Shutdown connection to server. Returns server ``BYE`` response.
|
|
|
|
.. versionchanged:: 3.8
|
|
The method no longer ignores silently arbitrary exceptions.
|
|
|
|
|
|
.. method:: IMAP4.lsub(directory='""', pattern='*')
|
|
|
|
List subscribed mailbox names in directory matching pattern. *directory*
|
|
defaults to the top level directory and *pattern* defaults to match any mailbox.
|
|
Returned data are tuples of message part envelope and data.
|
|
|
|
|
|
.. method:: IMAP4.myrights(mailbox)
|
|
|
|
Show my ACLs for a mailbox (i.e. the rights that I have on mailbox).
|
|
|
|
|
|
.. method:: IMAP4.namespace()
|
|
|
|
Returns IMAP namespaces as defined in :rfc:`2342`.
|
|
|
|
|
|
.. method:: IMAP4.noop()
|
|
|
|
Send ``NOOP`` to server.
|
|
|
|
|
|
.. method:: IMAP4.open(host, port, timeout=None)
|
|
|
|
Opens socket to *port* at *host*. The optional *timeout* parameter
|
|
specifies a timeout in seconds for the connection attempt.
|
|
If timeout is not given or is ``None``, the global default socket timeout
|
|
is used. Also note that if the *timeout* parameter is set to be zero,
|
|
it will raise a :class:`ValueError` to reject creating a non-blocking socket.
|
|
This method is implicitly called by the :class:`IMAP4` constructor.
|
|
The connection objects established by this method will be used in
|
|
the :meth:`IMAP4.read`, :meth:`IMAP4.readline`, :meth:`IMAP4.send`,
|
|
and :meth:`IMAP4.shutdown` methods. You may override this method.
|
|
|
|
.. audit-event:: imaplib.open self,host,port imaplib.IMAP4.open
|
|
|
|
.. versionchanged:: 3.9
|
|
The *timeout* parameter was added.
|
|
|
|
.. method:: IMAP4.partial(message_num, message_part, start, length)
|
|
|
|
Fetch truncated part of a message. Returned data is a tuple of message part
|
|
envelope and data.
|
|
|
|
|
|
.. method:: IMAP4.proxyauth(user)
|
|
|
|
Assume authentication as *user*. Allows an authorised administrator to proxy
|
|
into any user's mailbox.
|
|
|
|
|
|
.. method:: IMAP4.read(size)
|
|
|
|
Reads *size* bytes from the remote server. You may override this method.
|
|
|
|
|
|
.. method:: IMAP4.readline()
|
|
|
|
Reads one line from the remote server. You may override this method.
|
|
|
|
|
|
.. method:: IMAP4.recent()
|
|
|
|
Prompt server for an update. Returned data is ``None`` if no new messages, else
|
|
value of ``RECENT`` response.
|
|
|
|
|
|
.. method:: IMAP4.rename(oldmailbox, newmailbox)
|
|
|
|
Rename mailbox named *oldmailbox* to *newmailbox*.
|
|
|
|
|
|
.. method:: IMAP4.response(code)
|
|
|
|
Return data for response *code* if received, or ``None``. Returns the given
|
|
code, instead of the usual type.
|
|
|
|
|
|
.. method:: IMAP4.search(charset, criterion[, ...])
|
|
|
|
Search mailbox for matching messages. *charset* may be ``None``, in which case
|
|
no ``CHARSET`` will be specified in the request to the server. The IMAP
|
|
protocol requires that at least one criterion be specified; an exception will be
|
|
raised when the server returns an error. *charset* must be ``None`` if
|
|
the ``UTF8=ACCEPT`` capability was enabled using the :meth:`enable`
|
|
command.
|
|
|
|
Example::
|
|
|
|
# M is a connected IMAP4 instance...
|
|
typ, msgnums = M.search(None, 'FROM', '"LDJ"')
|
|
|
|
# or:
|
|
typ, msgnums = M.search(None, '(FROM "LDJ")')
|
|
|
|
|
|
.. method:: IMAP4.select(mailbox='INBOX', readonly=False)
|
|
|
|
Select a mailbox. Returned data is the count of messages in *mailbox*
|
|
(``EXISTS`` response). The default *mailbox* is ``'INBOX'``. If the *readonly*
|
|
flag is set, modifications to the mailbox are not allowed.
|
|
|
|
|
|
.. method:: IMAP4.send(data)
|
|
|
|
Sends ``data`` to the remote server. You may override this method.
|
|
|
|
.. audit-event:: imaplib.send self,data imaplib.IMAP4.send
|
|
|
|
|
|
.. method:: IMAP4.setacl(mailbox, who, what)
|
|
|
|
Set an ``ACL`` for *mailbox*. The method is non-standard, but is supported by
|
|
the ``Cyrus`` server.
|
|
|
|
|
|
.. method:: IMAP4.setannotation(mailbox, entry, attribute[, ...])
|
|
|
|
Set ``ANNOTATION``\ s for *mailbox*. The method is non-standard, but is
|
|
supported by the ``Cyrus`` server.
|
|
|
|
|
|
.. method:: IMAP4.setquota(root, limits)
|
|
|
|
Set the ``quota`` *root*'s resource *limits*. This method is part of the IMAP4
|
|
QUOTA extension defined in rfc2087.
|
|
|
|
|
|
.. method:: IMAP4.shutdown()
|
|
|
|
Close connection established in ``open``. This method is implicitly
|
|
called by :meth:`IMAP4.logout`. You may override this method.
|
|
|
|
|
|
.. method:: IMAP4.socket()
|
|
|
|
Returns socket instance used to connect to server.
|
|
|
|
|
|
.. method:: IMAP4.sort(sort_criteria, charset, search_criterion[, ...])
|
|
|
|
The ``sort`` command is a variant of ``search`` with sorting semantics for the
|
|
results. Returned data contains a space separated list of matching message
|
|
numbers.
|
|
|
|
Sort has two arguments before the *search_criterion* argument(s); a
|
|
parenthesized list of *sort_criteria*, and the searching *charset*. Note that
|
|
unlike ``search``, the searching *charset* argument is mandatory. There is also
|
|
a ``uid sort`` command which corresponds to ``sort`` the way that ``uid search``
|
|
corresponds to ``search``. The ``sort`` command first searches the mailbox for
|
|
messages that match the given searching criteria using the charset argument for
|
|
the interpretation of strings in the searching criteria. It then returns the
|
|
numbers of matching messages.
|
|
|
|
This is an ``IMAP4rev1`` extension command.
|
|
|
|
|
|
.. method:: IMAP4.starttls(ssl_context=None)
|
|
|
|
Send a ``STARTTLS`` command. The *ssl_context* argument is optional
|
|
and should be a :class:`ssl.SSLContext` object. This will enable
|
|
encryption on the IMAP connection. Please read :ref:`ssl-security` for
|
|
best practices.
|
|
|
|
.. versionadded:: 3.2
|
|
|
|
.. versionchanged:: 3.4
|
|
The method now supports hostname check with
|
|
:attr:`ssl.SSLContext.check_hostname` and *Server Name Indication* (see
|
|
:const:`ssl.HAS_SNI`).
|
|
|
|
|
|
.. method:: IMAP4.status(mailbox, names)
|
|
|
|
Request named status conditions for *mailbox*.
|
|
|
|
|
|
.. method:: IMAP4.store(message_set, command, flag_list)
|
|
|
|
Alters flag dispositions for messages in mailbox. *command* is specified by
|
|
section 6.4.6 of :rfc:`2060` as being one of "FLAGS", "+FLAGS", or "-FLAGS",
|
|
optionally with a suffix of ".SILENT".
|
|
|
|
For example, to set the delete flag on all messages::
|
|
|
|
typ, data = M.search(None, 'ALL')
|
|
for num in data[0].split():
|
|
M.store(num, '+FLAGS', '\\Deleted')
|
|
M.expunge()
|
|
|
|
.. note::
|
|
|
|
Creating flags containing ']' (for example: "[test]") violates
|
|
:rfc:`3501` (the IMAP protocol). However, imaplib has historically
|
|
allowed creation of such tags, and popular IMAP servers, such as Gmail,
|
|
accept and produce such flags. There are non-Python programs which also
|
|
create such tags. Although it is an RFC violation and IMAP clients and
|
|
servers are supposed to be strict, imaplib still continues to allow
|
|
such tags to be created for backward compatibility reasons, and as of
|
|
Python 3.6, handles them if they are sent from the server, since this
|
|
improves real-world compatibility.
|
|
|
|
.. method:: IMAP4.subscribe(mailbox)
|
|
|
|
Subscribe to new mailbox.
|
|
|
|
|
|
.. method:: IMAP4.thread(threading_algorithm, charset, search_criterion[, ...])
|
|
|
|
The ``thread`` command is a variant of ``search`` with threading semantics for
|
|
the results. Returned data contains a space separated list of thread members.
|
|
|
|
Thread members consist of zero or more messages numbers, delimited by spaces,
|
|
indicating successive parent and child.
|
|
|
|
Thread has two arguments before the *search_criterion* argument(s); a
|
|
*threading_algorithm*, and the searching *charset*. Note that unlike
|
|
``search``, the searching *charset* argument is mandatory. There is also a
|
|
``uid thread`` command which corresponds to ``thread`` the way that ``uid
|
|
search`` corresponds to ``search``. The ``thread`` command first searches the
|
|
mailbox for messages that match the given searching criteria using the *charset*
|
|
argument for the interpretation of strings in the searching criteria. It then
|
|
returns the matching messages threaded according to the specified threading
|
|
algorithm.
|
|
|
|
This is an ``IMAP4rev1`` extension command.
|
|
|
|
|
|
.. method:: IMAP4.uid(command, arg[, ...])
|
|
|
|
Execute command args with messages identified by UID, rather than message
|
|
number. Returns response appropriate to command. At least one argument must be
|
|
supplied; if none are provided, the server will return an error and an exception
|
|
will be raised.
|
|
|
|
|
|
.. method:: IMAP4.unsubscribe(mailbox)
|
|
|
|
Unsubscribe from old mailbox.
|
|
|
|
.. method:: IMAP4.unselect()
|
|
|
|
:meth:`imaplib.IMAP4.unselect` frees server's resources associated with the
|
|
selected mailbox and returns the server to the authenticated
|
|
state. This command performs the same actions as :meth:`imaplib.IMAP4.close`, except
|
|
that no messages are permanently removed from the currently
|
|
selected mailbox.
|
|
|
|
.. versionadded:: 3.9
|
|
|
|
.. method:: IMAP4.xatom(name[, ...])
|
|
|
|
Allow simple extension commands notified by server in ``CAPABILITY`` response.
|
|
|
|
|
|
The following attributes are defined on instances of :class:`IMAP4`:
|
|
|
|
.. attribute:: IMAP4.PROTOCOL_VERSION
|
|
|
|
The most recent supported protocol in the ``CAPABILITY`` response from the
|
|
server.
|
|
|
|
|
|
.. attribute:: IMAP4.debug
|
|
|
|
Integer value to control debugging output. The initialize value is taken from
|
|
the module variable ``Debug``. Values greater than three trace each command.
|
|
|
|
|
|
.. attribute:: IMAP4.utf8_enabled
|
|
|
|
Boolean value that is normally ``False``, but is set to ``True`` if an
|
|
:meth:`enable` command is successfully issued for the ``UTF8=ACCEPT``
|
|
capability.
|
|
|
|
.. versionadded:: 3.5
|
|
|
|
|
|
.. _imap4-example:
|
|
|
|
IMAP4 Example
|
|
-------------
|
|
|
|
Here is a minimal example (without error checking) that opens a mailbox and
|
|
retrieves and prints all messages::
|
|
|
|
import getpass, imaplib
|
|
|
|
M = imaplib.IMAP4(host='example.org')
|
|
M.login(getpass.getuser(), getpass.getpass())
|
|
M.select()
|
|
typ, data = M.search(None, 'ALL')
|
|
for num in data[0].split():
|
|
typ, data = M.fetch(num, '(RFC822)')
|
|
print('Message %s\n%s\n' % (num, data[0][1]))
|
|
M.close()
|
|
M.logout()
|
|
|