From a novice, today we had an experience of all our email basically
shutdown and users could not register, recover passwords or login with email because the weekly digest kicked off after a legacy forum migration and there were over 300K emails in the
sidekiq queue; so anyone who tried to login via email, register, recover their password, etc did not get any email and were
hosed (as they say)…
The issue was based on the fact that we use GMAIL as our mail relay, and (free) GMAIL set limits on this sort of SMTP relaying and so GMAIL shut us down for the day.
I would like to ask for this feature in the future (unless there is another way to address this).
Add another set of
app.yml vars which permit admins to set up a different email relay for digests.
During the setup process, the dialog could add
Do you want to set up a different SMTP server for digests? and the user could use the same SMTP relay if they wished.
For large forums with a lot of digest activity, it would be good to have an option to relay these digest emails via a different SMTP relay than the one used for the key tasks, like password recovery, login and registration.
For now, we have turned off all digests. We did see a way to limit this the seen in last
X number of days setting. The default, when I was checking it out today, was 365 days. For some reason, our migrated server queued up over 300K messages.
It’s not a huge issue, but it would be good, I think, to separate
mission critical emails; because even if the
queuing priority is higher for
mission critical emails, if the SMTP relay blocks because of an excessive number of digests, the
mission critical email will be blocked as well.
In addition, some forums may be experiencing a similar situation and not be aware of why their SMTP mail is not working; when in fact it was blocked for the reason mentioned.
Thank you for your thoughtful consideration.