I'd like to fetch the whole message from IMAP4 server. In python docs if found this bit of code that works:
>>> t, data = M.fetch('1', '(RFC822)')
>>> body = data[0][1]
I'm wondering if I can always trust that data[0][1] returns the body of the message. When I've run 'RFC822.SIZE' I've got just a string instead of a tuple.
I've skimmed through rfc1730 but I wasn't able to figure out the proper response structure for the 'RFC822'. It is also hard to tell the fetch result structure from imaplib documentation.
Here is what I'm getting when fetching RFC822
:
('OK', [('1 (RFC822 {858569}', 'body of the message', ')')])
But when I fetch RFC822.SIZE
I'm getting:
('OK', ['1 (RFC822.SIZE 847403)'])
How should I properly handle the data[0] list? Can I trust that when it is a list of tuples the tuples has exactly 3 parts and the second part is the payload?
Maybe you know any better library for imap4?
This was my solution to extract the useful bits of information. It's been reliable so far:
The IMAPClient package is a fair bit easier to work with. From the description:
No...
imaplib
is a pretty good library, it's imap that's so unintelligible.You may wish to check that
t == 'OK'
, butdata[0][1]
works as expected for as much as I've used it.Here's a quick example I use to extract signed certificates I've received by email, not bomb-proof, but suits my purposes:
You may use imap_tools package: https://pypi.org/project/imap-tools/
Features:
example: