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
Week ending January 30, 2022
*Triaged: *
https://code.djangoproject.com/ticket/33459 - Explain how to optimize
full text search with SearchVectorField and GinIndex (wontfix)
https://code.djangoproject.com/ticket/33460 - Change SQLite backend to
generate INSERT statements using VALUES
Week ending January 23, 2022
*Triaged: *
https://code.djangoproject.com/ticket/33444 - Add an option with default
answer for makemigrations questions. (wontfix)
https://code.djangoproject.com/ticket/33443 - Conditions when
PasswordResetView sends email should be listed more clearly
Thanks. We will work on it later this week.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Another situation you might want multiple backends is when switching
providers. Rather than big-bang swap *all* email sends to a new provider,
you might want to move only low-value emails first, or a percentage of your
user base, and iterate.
On Sun, 30 Jan 2022 at 20:59, Steven Mapes wrote:
>
I should add I also have other instances my clients use a custom AWS SES
backend I wrote used for various types of sends (bulk, newsletters) but
generally sends where they need SNS notifications to trigger HTTPS postbacks
for certain results from the send such as bounced mails, spam reports etc
I have clients that use different mailboxes sometimes with totally different
providers (O365, Google, their own mailservers) so they need different SMTP
settings. In some cases they also read from the mailboxes, granted this isn't
from Django builtin functionality but in those cases it uses the
+1 from our side as well.
Another common scenario for us is mail server reputation: We use different
providers for transactional and newsletter emails as well as different
servers depending on the users plan (enterprise customers have a more
reliable but more expensive mail server opposed to
Maybe we're doing something stupid or there's a misunderstanding but we had
a recent use case for this: The same website runs on several domains, one
domain per language and each domain has its own email address. We were
using an email relay (Mailgun in this case but the same will probably be
true
I do not understand why you would need multiple email backends to send from
different addresses. Can you elaborate on that?
On Sunday, January 30, 2022 at 1:18:48 PM UTC+1 st...@jigsawtech.co.uk
wrote:
> I've a big +1 on changing email config to a dictionary to support multiple
> backends as
I've a big +1 on changing email config to a dictionary to support multiple
backends as it's very much a common occurrence for both clients of mine and
for my own businesses. Most of the use cases are when they main site sends
emails from no-reply@ such as for password resets but then when
Hi Jacob,
I wouldn't be opposed to move email configuration into a dictionary
(somewhere between -0 and +0). Although if we plan to do that we should
rethink all the existing session variables and other as well I guess and
figure out if we should move more settings to dictionaries.
> why
Well, that ticket is 8 years old and in the meantime other email backends
have emerged, requiring different configuration options.
I made this proposal after attempting to fix a 14 year old open ticket
#6989 but this was ultimately postponed, see comment by
Carlton Gibson on
13 matches
Mail list logo
