On 21 Aug 2009, at 11:39, Tim Chase wrote: > Having email settings defined globally precludes the ability to > do things like create a web email application for which each user > has their own email (usually SMTP/IMAP/POP) settings. While yes, > I could see having some defaults at the settings.py level, it > should be possible to override those at the call level.
It would be easy to do so. Since signal receivers can be dynamically connected and disconnected, it would be relatively trivial to implement a function which would dynamically create a receiver with a UUID, use it for sending messages via that single connection, and then destroy the receiver again afterwards. But still, the top-level functions for sending e-mails should be backend-agnostic, which means they shouldn’t accept any SMTP-specific arguments, and so developers should really be putting their default configuration into the settings module. -- Zack --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
