Jacob Rief

I see both pull requests as completely independent. That one I fixed was accepted by Malcolm Tredinnick in 2010. Very sad that we can't ask him anymore. Having to override...

@MaicoTimmerman > I think the scope of this patch could be broadened a little more. Currently, it only improves the message-ID and names the setting accordingly. However, the EHLO/HELO SMTP...

Moving the Email backend out of Django (but as part of the ecosystem), certainly is an option we shall talk about. This however removes one battery, otherwise included into the...

@carltongibson I'm completely with you. This probably is the beast approach! As a side note, a more modular configuration system would be highly appreciated: Then each component gets its own...

@carltongibson @MaicoTimmerman I will update this pull request, if we can agree, that `EMAIL_FQDN` is the proper name for this configuration directive.

@carltongibson > I can't push this forwards unless it's actually in the "yes, this is the proposed change" state. From the discussion that's not the case. What can I do...

@MaicoTimmerman @carltongibson I'm willing to push this forward, but the Django board must agree on details, for instance if `EMAIL_FQDN` is the right name for this extra settings variable. I...

@carltongibson wouldn't it then make sense, to allow multiple SMTP backends, similar to the database? In the project's `settings.py` this then would look like: ```python EMAIL = { 'default': {...

> Interesting. I hadn't considered that option — is it something you'd want? (Moving the config into the backend would allow multiple backends so it's certainly related.) For consistency it...

I moved this issue to the discussion group: https://groups.google.com/g/django-developers/c/R8ebGynQjK0 Please provide feedback, because as it seems currently we're stuck on this.