If your app just sends email upon registration or just configured to send mail generally and you would like to use an email with your production domain like in a production setting, then you only need to change the email configuration in your settings.py file to reflect your domain email. For example, get your production domain, www.example.com, create an email account under that domain name, e.g support@example.com, then use this as your default email in your settings.py file. Typically your Email Host would just be your domain name, the port for HTTPS would be the same, but the settings would most likely be shown to you from wherever you are hosting the domain from.
On Tue, May 25, 2021 at 07:18 Antonis Christofides <antonis@antonischristofides.com> wrote:
using Sendmail code that we added in our Django projectYou really added sendmail code to your Django project? Or did you configure your Django project to use sendmail?There is no single answer to what you are asking. What I do, and I also propose to people to do, is:
- Use a small forward-only local name server, namely the DragonFly Mail Agent or dma.
- Use an external service like Runbox or mailbox.org as a mail server. I think that paid Google mail accounts will also work.
As for regularly emailing members, again I'd use an external service such as mailchimp, but I have no experience integrating such a service with a Django app.
Antonis Christofides +30-6979924665 (mobile)--
On 25/05/2021 08.02, Ram wrote:
--Hi,
We have members registration module where members will enter email ID as a login name. Upon submitting the Sign Up form, we generate an email to the given email address using Sendmail code that we added in our Django project.
So far we used a personal gmail account as an admin email account to generate and send emails to registered members ( as shown below)
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' # added by me
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_PORT = 587
EMAIL_HOST_USER = 'xxadmin@gmail.com'
EMAIL_HOST_PASSWORD = '122hhhlll'
EMAIL_USE_TLS = True
but we need to move on to next step on our development and production servers to have a real time admin email to handle member registrations and further communication with members, like sending newsletters and some important security notifications.
Could you please suggest what you been using with zero issues in your Django application?
Best regards,
~Ram
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F0C17vnf4vEvZgMYha0b2XB49iZpJ4UzqKb56-Tmar-cQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e8186cd2-9a0e-899c-227f-489ae74cf227%40antonischristofides.com.
KeLLs
-- You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADYqDX0-cE-aogajOdeQCWZ0NfL929gp7pz1OnoceE2Zwg%3DzwA%40mail.gmail.com.
No comments:
Post a Comment