Mail Activitiesal
This Python package contains Mail class to work with emails, for more information about how to develop your RPA projects with python check https://automatehub.es/
Mail class
The Mail class represents a mail account and provides methods for sending and fetching emails.
Arguments
email: The email address of the mail account.password: The password of the mail account.smtp_server: The SMTP server of the mail account.smtp_port: The SMTP port of the mail account.imap_server: The IMAP server of the mail account.imap_port: The IMAP port of the mail account.
Attributes
username: The username of the mail account.password: The password of the mail account.smtp_server: The SMTP server of the mail account.smtp_port: The SMTP port of the mail account.imap_server: The IMAP server of the mail account.imap_port: The IMAP port of the mail account.
Methods
send(send_to, subject, text=None, html=None, files=None)
The send method is used to send an email.
Arguments
send_to: The email address to send the email to.subject: The subject of the email.text(optional): The text content of the email.html(optional): The HTML content of the email.files(optional): A list of files to attach to the email.
fetch(folder, Query)
The fetch method is used to fetch a list of emails from the mail box.
Arguments
folder: The folder to fetch emails from.Query: A query object used to filter the emails. More information about theQueryobject can be found here.
download_attachments
This function is used to download attachments from a mail message.
Arguments:
-
mail: AMailMessageobject representing the mail from which attachments need to be downloaded. -
download_folder: The folder where the attachments will be downloaded to. -
extension: (Optional) The extension of the attachments to be downloaded. If specified, only attachments with this extension will be downloaded. If not specified, all attachments will be downloaded.
More information
For more information about the Mail class and the Query object, please refer to the IMAP Tools documentation.
Metadata
Release files for ibott-mail 1.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ibott-mail-1.0.7.tar.gz | 8.8 kB | Without provenance | Details for ibott-mail-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ibott_mail-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for ibott_mail-1.0.7-py3-none-any.whl |
Total release size: 20.8 kB
Release files / ibott-mail-1.0.7.tar.gz
| Download URL | ibott-mail-1.0.7.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2395618385ef7f788f6414ce8dccb8bac13eb7a387c1aecb58d2b7294186756
|
|
BLAKE2b-256 checksum How to use checksums |
ccdfe90c8bceb8105f3a711c45b792af945a1856573f0c813afa1036e1484b80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / ibott_mail-1.0.7-py3-none-any.whl
| Download URL | ibott_mail-1.0.7-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
992a449444edd1f5f7629dcc7da618da5c5874840a4a6bd86b83f11fccd722be
|
|
BLAKE2b-256 checksum How to use checksums |
1927cf5781d4802b329709a11eb6edc41a3ccaa1635bef0b006f9d6be1418949
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for ibott-mail 1.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.