Hi Andrew, On Thu, May 9, 2019 at 10:04 PM Andrew Godwin <and...@aeracode.org> wrote:
> > If you want guaranteed email delivery, that's a task for something like > Celery or a third-party API; any method of sending emails in the background > in the same process, be it threads or async coroutines, is going to be > unreliable as the server may die any time. I don't think it's sensible for > Django to try and solve this problem internally, at least not as part of > this async push. > I'm a bit confused here, what benefit are you getting from async emails if you're already retrying emails in the background in production ? Thanks for your kind reply, Have a great day -- ∞ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18AA3Q7wguoZn%3D%2BfqHTAquXU0cESxF2i0GYzp%2BjB_ft%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
