Hey, We run our own custom EmailBackend, and for the most part the new Email Backend system has been fantastic, however recently I just found a limitation, which I'd like to raise briefly to see if anyone else has it, or can suggest an obvious solution Ive missed.
We currently have a queued email backend which communicates with external services to send email on our behalf. When our main newsletters go out, this causes a huge spike in the system and queues pile up. This is fine except that we want some email to now bypass the queue, for example registration emails. This is because the queues often take 3-4 hours to process and this is an unacceptable delay for signup emails. So essentially we would like to be able to use a different backend for different circumstances, or be able to pass args/kwargs into the backend from the send() to allow the EmailBackend to make the appropriate routing changes. Any thoughts on this as a change to the Email Backend system in django? Mat -- -- Matthew Clayton | Founder/CEO Wakari Limited twitter http://www.twitter.com/matclayton email [email protected] mobile +44 7872007851 skype matclayton -- 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.
