From 2655cad028002fae148e2e2e4ba57755b5d0e389 Mon Sep 17 00:00:00 2001 From: yoshiki masubuchi Date: Sun, 22 Oct 2023 22:41:42 +0900 Subject: [PATCH] Improve action_mailbox_basics.md --- guides/source/action_mailbox_basics.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/guides/source/action_mailbox_basics.md b/guides/source/action_mailbox_basics.md index fb099cfdff2d3..91af99a00c0b3 100644 --- a/guides/source/action_mailbox_basics.md +++ b/guides/source/action_mailbox_basics.md @@ -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