aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Heinemeier Hansson <david@loudthinking.com>2018-12-12 16:06:56 -0800
committerDavid Heinemeier Hansson <david@loudthinking.com>2018-12-12 16:06:56 -0800
commit1df26841b34d065c111d9b4e2147c1f94ec70c7d (patch)
tree93a17ee02e5924def1e8b5a25be1e9df2a85b0a9
parentde5e4d1936ddb5fd744c094f1c97e67c732bd542 (diff)
downloadrails-1df26841b34d065c111d9b4e2147c1f94ec70c7d.tar.gz
rails-1df26841b34d065c111d9b4e2147c1f94ec70c7d.tar.bz2
rails-1df26841b34d065c111d9b4e2147c1f94ec70c7d.zip
Note about incineration
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index db55cf197b..d779d8adcc 100644
--- a/README.md
+++ b/README.md
@@ -89,6 +89,12 @@ class ForwardsMailbox < ApplicationMailbox
end
```
+## Incineration of InboundEmails
+
+By default, an InboundEmail that has been marked as 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 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 for the extra time to provide debugging and forensics options.
+
+The actual incineration is done via the `IncinerationJob` that's scheduled to run after `config.action_mailbox.incinerate_after` time. This value is 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.)
+
## Create incoming email through a conductor module in development