#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 Mike Edmunds):
Multiple email backends with dictionary-based config landed in Django 6.1.
I think it now makes sense to add a `local_hostname` option to the SMTP
EmailBackend. (Only through a `MAILERS` OPTIONS dict, not a new top-level
setting.)
[Btw, subclassing the SMTP backend to override local_hostname would
require duplicating the entire `open()` method, at least as the code is
currently structured. And the subclass would then need to carefully track
changes in the base class for things like the recent security fix. I'm not
sure subclassing is a realistic solution for this specific issue.]
--
Ticket URL: <https://code.djangoproject.com/ticket/6989#comment:26>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019ec2575a26-92607cda-1e97-430a-aa15-fab4ff638400-000000%40eu-central-1.amazonses.com.
