#6989: Inability to define DNS_NAME in django.core.mail results in e-mail
messages
being rejected or marked as spam
-------------------------------------+-------------------------------------
Reporter: Franklin | Owner: nobody
Type: Bug | Status: new
Component: Core (Mail) | Version: master
Severity: Normal | Resolution:
Keywords: local_hostname, | Triage Stage: Accepted
DNS_NAME, CachedDnsName, smtplib, | Needs documentation: 1
SMTPConnection | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by russellm):
@davidgrant - Where do we go? We go the same way we do with any other
ticket that has stalled: Start a discussion on django-dev. Summarize the
problem. Summarize the alternatives. Propose a solution.
I'll also note that Adrian's comment about settings -- we've historically
avoided adding new settings wherever possible. But if it truly isn't
possible (at all, or for all practical purposes) to avoid a setting, it's
not completely off the cards.
--
Ticket URL: <https://code.djangoproject.com/ticket/6989#comment:16>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f18eef5b0bb82ccf295cd3ae4bac5535%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
