Reference
Auto-expunge
Configures data retention policies, expunge schedules, and archival settings.
On this page
- Other settings
- Archive deleted accounts for
- Archive deleted items for
- Blob cleanup schedule
- Data cleanup schedule
- Expunge schedule
- Expunge scheduling inbox after
- Expunge share notify after
- Expunge submissions after
- Expunge trash after
- Hold metrics for
- Hold MTA reports for
- Hold traces for
- Max changes history
- Metrics collection interval
In the console: Settings › Storage › Auto-expunge
Configures data retention policies, expunge schedules, and archival settings.
Other settings
Archive deleted accounts for
How long to keep deleted accounts in the archive before they are permanently deleted. If null, deleted accounts will be permanently deleted immediately.
A length of time. Name in the API: archiveDeletedAccountsFor.
Archive deleted items for
How long to keep deleted items in the archive before they are permanently deleted. If null, deleted items will not be archived and will be permanently deleted immediately.
A length of time. Name in the API: archiveDeletedItemsFor.
Blob cleanup schedule
How often to purge the data store. Expects a cron expression.
Settings of their own: see Cron. Default: Every day. Name in the API: blobCleanupSchedule.
Data cleanup schedule
How often to purge the data store. Expects a cron expression.
Settings of their own: see Cron. Default: Every day. Name in the API: dataCleanupSchedule.
Expunge schedule
Specifies when to run the auto-expunge process.
Settings of their own: see Cron. Default: Every day. Name in the API: expungeSchedule.
Expunge scheduling inbox after
Sets the duration after which the iTIP inbox will automatically expunge old messages.
A length of time. Default: 30d. Name in the API: expungeSchedulingInboxAfter.
Expunge share notify after
Specifies the duration for which the JMAP share notification history is retained before it is automatically purged.
A length of time. Default: 30d. Name in the API: expungeShareNotifyAfter.
Expunge submissions after
How long to keep sent e-mail submissions before auto-expunging.
A length of time. Default: 3d. Name in the API: expungeSubmissionsAfter.
Expunge trash after
How long to keep messages in the Trash and Junk Mail folders before auto-expunging.
A length of time. Default: 30d. Name in the API: expungeTrashAfter.
Hold metrics for
How long to keep metrics history before it is permanently deleted.
A length of time. Default: 90d. Name in the API: holdMetricsFor.
Hold MTA reports for
The duration for which MTA reports should be stored before being deleted, or None to disable storage.
A length of time. Default: 30d. Name in the API: holdMtaReportsFor.
Hold traces for
How long to keep message delivery history before it is permanently deleted.
A length of time. Default: 30d. Name in the API: holdTracesFor.
Max changes history
How many changes to keep in the history for each account. This is used to determine the changes that have occurred since the last time the client requested changes.
A number. Default: 10000. Name in the API: maxChangesHistory.
Metrics collection interval
Specifies how often to collect metrics history.
Settings of their own: see Cron. Default: Every hour. Name in the API: metricsCollectionInterval.