-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of Flask-Mail #531
Comments
Thanks for the idea and the pointer to a newer mail package. I'll look into doing something like I did for flask-babelex versus flask-babel - import one or the other... |
flask-mail has been abandoned - flask-mailman is a newer package that provides similar functionality to Django mail. Use flask-mailmanas our default and in all the examples. flask-mail is still supported - and of course from a runtime perspective this all can be easily overwritten using the MailUtil class. Most changes were around flask-mailman having a different way of capturing outbound emails during testing. Closes: #531
flask-mail has been abandoned - flask-mailman is a newer package that provides similar functionality to Django mail. Use flask-mailmanas our default and in all the examples. flask-mail is still supported - and of course from a runtime perspective this all can be easily overwritten using the MailUtil class. Most changes were around flask-mailman having a different way of capturing outbound emails during testing. Closes: #531
flask-mail has been abandoned - flask-mailman is a newer package that provides similar functionality to Django mail. Use flask-mailmanas our default and in all the examples. flask-mail is still supported - and of course from a runtime perspective this all can be easily overwritten using the MailUtil class. Most changes were around flask-mailman having a different way of capturing outbound emails during testing. Closes: #531
FYI: There is a new Flask-Mail version. 😮 https://github.com/pallets-eco/flask-mail/releases/tag/0.10.0 |
Yea - saw that - not a big deal to support it again.... As an aside - I am in the process of working with pallets to move flask-security under their repo and become the 'one' flask-security (including pypi). |
Flask-Mail is unmaintained since 2014 (as you know, I think 😉). Since there are security related issues, I want to suggest to get rid of this dependency. @waynerv has ported Django's email implementation to a Flask extension. So this may be an alternative.
What do you think? I know, this would be a major change. But actually, Flask-Security contains a lot of unmaintained dependencies (Flask-Mail, Flask-Principal, pyqrcode) and I think it would be a chance to improve this project.
Best Pascua
The text was updated successfully, but these errors were encountered: