-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance on sending emails to many subusers (100+) #623
Comments
Definitely very curious how this use case is handled! |
If all that's needed it to be able to set the
Would this work for your usecase? |
I'm trying to actually send emails, and the Sendgrid docs claim that On-Behalf-Of is not supported for mail.send :(: https://sendgrid.api-docs.io/v3.0/how-to-use-the-sendgrid-v3-api/on-behalf-of |
Ah, TIL. We could update the library to lazily-create the fixed thread pool, so it would be created on the first call to |
Issue Summary
I'm trying to use this library to send emails on behalf of many subusers - in the hundreds, if not thousands. It appears that the primary pattern is to use
new Sendgrid(apiKey)
in order to send - but that creates a FixedThreadPool with 8 threads. If I wish to send emails to even 10 subusers, this means I'll have 10 FixedThreadPools with 8 threads each - not desirable.Is there any guidance on how to appropriately use this library for the above use-case? It looks like we could implemented
SendgridAPI
, but I'm hoping to avoid that if possible.I'd use
on-behalf-of
, but that is not supported formail.send
.Technical details:
The text was updated successfully, but these errors were encountered: