#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 Alexander Lazarević):
I'm trying to understand the status of this ticket and the problem. I
traced the discussion here, on the PR and google groups ...
The end of the discussion in google groups seems to be:
{{{
Jacob Rief 31 Jan 2022, 15:36:40 to Django developers (Contributions to
Django itself)
On Monday, January 31, 2022 at 7:55:47 AM UTC+1 [email protected] wrote:
Okay then,
some of the things like sender reputation and different bounce hooks
came to my mind as well, but it is good to hear confirmation from others.
I think the next steps would be to create a new ticket to add support for
*multiple* email backends and then work from that (I would only link the
old ticket since it's scope was mainly putting the config into a dict as
opposed to multiple backends). Given that there are plenty of +1 here
already I think we already have our implementors? :)
Some items that I like to see addressed in a PR:
* Backwards compat
* Similarity to Caches & Databases (ie so we don't invent yet another
syntax)
* Support for connection aliases (default/…) in send_email % friends
(basically everything taking a connection now should probably take aliases
as well)
OK. Since I made the proposal, it then is probably up to me to create the
ticket.
Mariusz Felisiak 1 Jun 2023, 21:48:04 to Django developers (Contributions
to Django itself)
It seems we have a consensus here to support multiple email backends.
Jacob, feel-free to create a new ticket.
Best, Mariusz
}}}
I couldn't find the Ticket by Jacob or anyone related to this.
A related ticket #31885 got fixed and closed. In the description it is
said that "We will then recommend subclassing in the docs for more
control. "
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)
Is the support for multiple email backends abandoned for now?
--
Ticket URL: <https://code.djangoproject.com/ticket/6989#comment:23>
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/0107018cfc32c241-236f2dd1-3062-4309-8a63-6b4758dff87f-000000%40eu-central-1.amazonses.com.
