Skip to content
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

Fix SES error preventing email to >50 recipients #9467

Open
dunkOnIT opened this issue Jun 3, 2024 · 2 comments
Open

Fix SES error preventing email to >50 recipients #9467

dunkOnIT opened this issue Jun 3, 2024 · 2 comments
Labels
TECH: ruby Requires knowledge of Ruby TYPE: bug Bug reported by a stakeholder

Comments

@dunkOnIT
Copy link
Contributor

dunkOnIT commented Jun 3, 2024

The following error was triggered when results for FMC 2024 were submitted - a competition with >50 delegates.
Net::SMTPFatalError (554 Transaction failed: Recipient count exceeds 50.

The following fixes should be implemented:

  • Short-term: Add a validation for when there are >=50 organizers/delegates on a competition (not sure if we need to check for delegates AND organizers, or just delegates)
  • Long-term: Do whatever we need to do to be able to send to >= 50 recipients
@dunkOnIT dunkOnIT added TYPE: bug Bug reported by a stakeholder TECH: ruby Requires knowledge of Ruby labels Jun 3, 2024
@gregorbg
Copy link
Member

gregorbg commented Jun 3, 2024

As per https://docs.aws.amazon.com/ses/latest/dg/quotas.html, adding more than 50 recipients is really not an option for AWS. We should probably implement a hard validation for this edge case in our own WCA code.

@FinnIckler
Copy link
Member

FinnIckler commented Jun 3, 2024

It also says that the best solution is just to send individual emails.

"Defining multiple recipients in a message destination can lead to poor observability as well as poor deliverability and should not be used unless your use case specifically requires it."

But they probably also have some bias i.e costs :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TECH: ruby Requires knowledge of Ruby TYPE: bug Bug reported by a stakeholder
Projects
None yet
Development

No branches or pull requests

3 participants