How to use a South data migration to avoid accidentally sending emails from example.com.
Consider the following snippet from Django's docs  for sending a confirmation email:
from django.contrib.sites.models import Site
from django.core.mail import send_mail
current_site = Site.objects.get_current()
'Thanks for subscribing to %s alerts' % current_site.name,
'Thanks for your subscription. We appreciate it.\n\n-The %s team.' % current_site.name,
'editor@%s' % current_site.domain,
)Here the domain for the email sender is taken from the 'current site' instance, which is controlled by Django's 'Sites' framework and accessible by a custom method on the manager of the Site model.
By default, a Site instance is created with domain and display name 'example.com' and you have to correct these values. This is often done by hand using the admin suite.
However, as with any manual change, it's easy to forget and you'll often find Django projects sending email from email@example.com
. Highly embarrassing.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/301743/viewspace-733299/，如需转载，请注明出处，否则将追究法律责任。