#6989: Inability to define DNS_NAME in django.core.mail results in e-mail
messages
being rejected or marked as spam
-------------------------------------+-------------------------------------
Reporter: Franklin | Owner: Jacob
| Rief
Type: Bug | Status: assigned
Component: Core (Mail) | Version: dev
Severity: Normal | Resolution:
Keywords: local_hostname, | Triage Stage: Accepted
DNS_NAME, CachedDnsName, smtplib, |
SMTPConnection |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:23 Alexander Lazarević]:
> Is subclassing now also the proposed method for setting a custom
DNS_NAME (or other option)? (I does not seemed to be mentioned in the
docs)
Yes, subclassing is basically a way to go for any fancy change to the
`EmailBackend` behavior.
> Is the support for multiple email backends abandoned for now?
Not really, it looks like no one had time to create a ticket. Please do if
you want.
--
Ticket URL: <https://code.djangoproject.com/ticket/6989#comment:24>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cfc8e6b7b-bb767479-a885-47b7-824c-051ea1ddba3d-000000%40eu-central-1.amazonses.com.
