Thanks for the explanations, but I'm still pretty convinced it may help :) The initial docs we have from one provider appear to use an API rather than SMTP apparently. Havn't looked into it yet myself, another one of our dev's is working on that section. not even sure if we will go with these guys, (exacttarget) if anyone has any thoughts on them please let me know off list.
Mat On Wed, Sep 2, 2009 at 3:14 PM, Russell Keith-Magee <[email protected]>wrote: > > On Wed, Sep 2, 2009 at 6:46 PM, Mat Clayton<[email protected]> wrote: > > I'm sure you have this covered but thought I would throw it into the mix. > We > > are currently having lots of problems with blacklisting and spam filters > > blocking our email servers, one way we are investigating to avoid this is > to > > outsource the email sending to trusted 3rd party services. We don't send > > unsolicited email (believe it or not), but being a social site, we send a > > fair amount of opt in emails, and for some reason this seems to be having > an > > impact on our registration confirmation emails getting blocked which is a > > real problem for us. Something like this mail backend system seems an > ideal > > solution to allow us to try and test alternatives. Just thought I would > > raise this as another reason why a pluggable backend would be a good > idea, > > it would certainly help in situations like ours. > > I'm not sure that this is the same problem. > > The goal of having pluggable email backends is to allow for mechanisms > other than SMTP for sending mail. The main driver for this is to > support AppEngine, but there are also benefits when testing. > > The situation you are describing is where you have multiple mail > servers, but they're all SMTP. In this case, you're still only using > one backend - you just have different configuration parameters > (hostname, port, password, etc). > > I presume the change SMTP server is something you need to be able to > do without restarting the server or updating settings. If this is the > case, this is already supported by instantiating multiple > SMTPConnection instances. The logic required to pick the right > SMTPConnection is something you would need to code yourself, as it > would be entirely site dependent. Having multiple backends won't help > you here - with Andi's code, all you will be doing is using > get_connection('smtp') to instantiate a connection, rather than using > SMTPConnection directly. > > The backend framework that has been proposed would allow you to write > a 'server-shifting backend' - that is, an email backend that > instantiates other email backends. This isn't really any different to > what you can do right now, except that it allows you to use the > send_mail() shortcut as well as EmailMessage(). > > Yours, > Russ Magee %-) > > > > -- -- 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 -~----------~----~----~----~------~----~------~--~---
