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
In SES the service will be suspended if the email bounce or complaint rate exceeds 10%. A warning is sent when the reputation complaint or bounce rate exceeds 5%. Due to the nature of mass email sends, it may be the case that the single email job can significantly exceed the reputation cutoff threshold in one job, leaving the service suspended. This is especially painful in a shared AWS account. Other Cloud privuiders may have different thresholds.
Would it be possible to stop the Moodle from sending emails when it is aware that the domain on which it sits is being marked up as exceeding these thresholds. So for example, all email cron jobs are paused when SES notifies of complaints/bounces reaching 5% (won't stop web/front end email jobs of course). In addition, ideally the plugin should notify site admins that this has occurred.
The text was updated successfully, but these errors were encountered:
In SES the service will be suspended if the email bounce or complaint rate exceeds 10%. A warning is sent when the reputation complaint or bounce rate exceeds 5%. Due to the nature of mass email sends, it may be the case that the single email job can significantly exceed the reputation cutoff threshold in one job, leaving the service suspended. This is especially painful in a shared AWS account. Other Cloud privuiders may have different thresholds.
Would it be possible to stop the Moodle from sending emails when it is aware that the domain on which it sits is being marked up as exceeding these thresholds. So for example, all email cron jobs are paused when SES notifies of complaints/bounces reaching 5% (won't stop web/front end email jobs of course). In addition, ideally the plugin should notify site admins that this has occurred.
The text was updated successfully, but these errors were encountered: