On Fri, Aug 21, 2009 at 12:39 PM, Tim Chase<[email protected]> wrote: > >> In terms of the SMTP-specific settings (host, port, username, password >> and use_tls), I personally feel that those parameters should be in the >> settings module and not in the code. Although at the moment, >> django.core.mail will use certain settings if said parameters are left >> out. > > 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.
A web-based email client needs probably a much more fine-grained access to the SMTP protocol to handle errors more accurate than an API that just sends out mails and simply fails (optional silently) when any error occurs. If you want to include this in Django's mail API, I suppose you end up with a smtplib clone :) POP and IMAP are totally different topics. > > -tim > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
