mirror of https://github.com/rails/rails
Improve action_mailbox_basics.md
This commit is contained in:
parent
6f6c211f47
commit
2655cad028
|
@ -324,9 +324,11 @@ end
|
|||
|
||||
## Incineration of InboundEmails
|
||||
|
||||
By default, an InboundEmail that has been successfully processed will be
|
||||
incinerated after 30 days. This ensures you're not holding on to people's data
|
||||
willy-nilly after they may have canceled their accounts or deleted their
|
||||
By default, an [`InboundEmail`][] that has been processed will be
|
||||
incinerated after 30 days. The InboundEmail is considered as processed
|
||||
when its status changes to delivered, failed or bounced.
|
||||
This ensures you're not holding on to people's data willy-nilly
|
||||
after they may have canceled their accounts or deleted their
|
||||
content. The intention is that after you've processed an email, you should have
|
||||
extracted all the data you needed and turned it into domain models and content
|
||||
on your side of the application. The InboundEmail simply stays in the system
|
||||
|
@ -338,6 +340,7 @@ by default set to `30.days`, but you can change it in your production.rb
|
|||
configuration. (Note that this far-future incineration scheduling relies on
|
||||
your job queue being able to hold jobs for that long.)
|
||||
|
||||
[`InboundEmail`]: https://edgeapi.rubyonrails.org/classes/ActionMailbox/InboundEmail.html
|
||||
[`config.action_mailbox.incinerate_after`]: configuring.html#config-action-mailbox-incinerate-after
|
||||
|
||||
## Working with Action Mailbox in Development
|
||||
|
|
Loading…
Reference in New Issue