You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe the title spoils it a little, but my buddy just sent out a mass-email to 250 people with everyone in the TO field because he could not find the BCC field in the Mail class (#1017) 🔥 🚒
Excuse me if this is a dumb request since I'm not very up-to-speed with the Sendgrid ecosystem. To me it seems a bit dangerous you can leak email addresses with such a simple silly developer mistake. Sure he should have been more careful, but what about making the default behavior a bit more safe, are there really people out there that want everyone in the TO field if there's 100+ addresses in TO?
But would it make sense to convert is_multiple to True somewhere under the hood when the TO field contains a list of length let's say larger than 50+? Or even better set a default is_multiple=True when len(to_emails)>1 ?
This would prevent someone in the future making the same mistake we did 😅 🙈
The text was updated successfully, but these errors were encountered:
Maybe the title spoils it a little, but my buddy just sent out a mass-email to 250 people with everyone in the TO field because he could not find the BCC field in the Mail class (#1017) 🔥 🚒
Excuse me if this is a dumb request since I'm not very up-to-speed with the Sendgrid ecosystem. To me it seems a bit dangerous you can leak email addresses with such a simple silly developer mistake. Sure he should have been more careful, but what about making the default behavior a bit more safe, are there really people out there that want everyone in the TO field if there's 100+ addresses in TO?
But would it make sense to convert
is_multiple
to True somewhere under the hood when the TO field contains a list of length let's say larger than 50+? Or even better set a defaultis_multiple=True
whenlen(to_emails)>1
?This would prevent someone in the future making the same mistake we did 😅 🙈
The text was updated successfully, but these errors were encountered: