pip install wrapmail
This module comes with a wrapper for Google's Gmail api. Google requires authentication for using the Gmail api. In order to use the wrapper, go to google developers console, create project, register Gmail api. The only required scope is https://mail.google.com/ Then, you need to download the client_secret json file and include it in your directory.
After you include client_secret.json and instantiated the Gmail class and run the main python file, and automatic authentication window will open and ask you to sign in. After signing in, if your authentication was successful you will be prompted by message "authentication flow has completed" and a pickle file will be created. As long as pickle file does not expire and is included in your working directory, you won't need to complete these steps. Do not share your client secret file, its contents or your pickle file. The authenticated email address will be used to send mails.
Since OAuth is used, you don't need to allow for less secure apps in your gmail account.
FAQs
A package that helps to send emails through Python utilizing an OOP logic
We found that wrapmail demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
