Deliver mail asynchronously via deliver_later#5530
Conversation
- Also adds a Rubocop linter to help keep us consistent
| - ./lib/linters/url_options_linter.rb | ||
| - ./lib/linters/localized_validation_message_linter.rb | ||
| - ./lib/linters/mail_later_linter.rb | ||
| - ./lib/linters/redirect_back_linter.rb | ||
| - ./lib/linters/url_options_linter.rb |
mitchellhenke
left a comment
There was a problem hiding this comment.
This looks good to me. Does it do retries, and do we want to limit that, e.g. so we don't send password reset emails after the code has expired?
Would we want to feature flag this?
I wasn't sure so I checked the the ActionMailer docs
and then the ActiveJob docs:
So my current believe is: no these will not be automatically retried.
Yeah I am open to feature flagging, do you have an approach? I'm thinking we could monkey patch on a method like |
I think that's the behavior we'd want for now, so sounds good.
That makes sense to me, if we can subclass the mailer or something, that'd be great. |
🤦 |
|
feature flag added in 11e64d6 |
- because it's called on the result of methods on ActionMailer::Base subclasses, not on the mailers themselves
Confirmed the worker hosts have correct SES permsision |
|
Admin overriding the diff coverage |
For all we know, there's some mail permission that's missing on the worker hosts so we need to confirm this works before merging