Hi, I'm interested in working on #10355 "Add support for email backends."
IMHO it's an good idea to make the email backend configurable. There are at least two use cases I can think of. The first is to send email with other services than SMTP, like App Engine as noted in the ticket's description. The second is to deliver email asynchronously, like the django-mailer application does already. The ticket currently needs a design decision, so my question is what the actual concerns to change this are. I would propose the following changes. It's a very simplistic approach that tries to keep the current API as much as possible: Add a new setting EMAIL_BACKEND. A string that can be resolved to a class. Default should be the current SMTP implementation. Provide a base class for mail backends. A mail backend must provide the method send_messages(email_messages) and must return the number of messages sent to provide backward compatibility. The constructor of a mail backend should take at least the keyword argument fail_silently (default: False). What I'm a bit unsure about are additional constructor arguments. Currently the SMTP backend allows in addition host, port, username, password and use_tls. Those are very SMTP-specific, but only username and password are used by the mail.send_mail* APIs. It would be an agreement to allow username and password in addition to fail_silently to not break the send_mail* API. The SMTP backend could accept host, port and use_tls as extra keywords again to provide backward compatibility for code that directly uses SMTPConnection (within Django SMTPConnection is not used outside django.core.mail). I would suggest to rename SMTPConnection to SMTPBackend, but only if this would break too much third-party code as SMTPConnection is mentioned in the docs. The test utils could be refactored to use a TestMailBackend instead of monkey-patching the mail module, but this would be a fairly invisible change as it would just change the way how the test utils provide the mailbox attribute in the mail module for unittests. A nice addition to Django would be to include parts of django-mailer to provide a backend for asynchronous mail delivery. That could be the models and command line script to deliver mails. While thinking about this, django-mailer has a nice option for setting priorities to mails. IMO Django's API for sending mails should be as simple as possible (like it is today), but a priority option would be a nice addition even if the SMTP backend (as the default) wouldn't respect this option when sending mails. Adding a App Engine backend is not covered here. I think it's up to third-party code to add support for sending mails on App Engine. However, such a backend would be pretty easy to implement. It would be nice to get some feedback on this suggestions and in a first step to find a design decision about #10355. Even if the decision is to not change anything for good reasons :) Regards, Andi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
