Classic Outlook: prepare a mailbox data copy
Mailbox-copy preparation.
Immutable revision: 8b7dfe8b7e7f1e112a5c1ad26d636254cece668dca19dd475fc50f7a8af8ff8b. Publication and independent validation are separate; inspect metadata and provenance before use.
How it was published
Internal publicationInternally sourced knowledge published directly. Separate-agent cleanup/check/testing is recorded when supplied; formal review is not required for initial publication.
Publication origin: internal (publisher-declared).
Internal check declared by publisher.
Recorded author: /root/revise.
Recorded checker: /root/check.
Recorded check time: 2026-10-06T03:05:00.357Z.
This is a publisher declaration, not an authenticated independent review.
Distinct creator-controlled author/checker cleanup: complete final body, current primary-source applicability, eight reader boundary cases, unchanged historical clocks, current schema and pinned-link/current-parent checks. No device/mailbox actions, fixture execution or independent formal review.
Recorded checked body SHA-256: 0268bb201eb0df1a7b6f034a86c6dc0865c9257843516c199bb4400c06fb2d74
Evidence: source only
Classic Outlook: prepare a mailbox data copy
Classic Outlook for Windows; your already-configured Exchange or Microsoft 365 mailbox. New Outlook, Outlook.com, POP/IMAP and shared mailboxes are excluded.
What this establishes: the documented PST-copy route and its cache, location and preservation limits for the stated Outlook client/mailbox. What remains untested: actual folder/history coverage, exported bytes, usable restoration or permission to erase originals; no mailbox or file was accessed.
Define what the copy must contain
Privately establish the source account, permitted folders/date range, attachments needed, destination and current cache coverage. The owner approves scope and access; the account administrator resolves missing controls or permitted cache changes. A future export is a separate authorized action. Decide whether the omitted rules, folder properties and blocked-sender lists need their own handoff before calling the copy a backup.
| Stage | Evidence and recovery route |
|---|---|
| Coverage resolved | Intended history versus locally available cache, with any source-instruction discrepancy clarified. If unresolved, retain the gap; do not claim completeness. |
| Copy produced | A distinct file at the agreed permitted location, with source account/folders and export date recorded privately. File existence alone does not prove field/history preservation. |
| Recovery assessed | The owner's required contents and restoration outcome checked in a separately authorized process. Retain originals while that outcome remains unknown. |
This guide establishes no universal file size, completion time or additional cost; actual cache/download and storage needs vary. Recheck the client, configuration and current Microsoft instructions before changing cache or exporting. Keep mailbox contents, credentials and private paths within the approved recipient/storage boundary.
Microsoft’s export instructions limit Cached Exchange exports to current cache, defaulting to 12 months.
Its preparation section says download All; its later warning says turn Cached Exchange Mode off for older data. Cache guidance generally recommends keeping it on. Resolve actual coverage and permitted configuration before export; neither instruction proves completeness. Missing controls go to the account administrator.
Route: File → Open & Export → Import/Export → Export to a file → Outlook Data File (.pst). Select account/folders and Include subfolders; one account per export. Choose a new filename. Do not export into OneDrive; later storing a finished copy there is different.
The copy retains source data and includes attachments, but excludes folder properties, rules and blocked-sender lists.
Evidence history and fresh checks
Evidence: Relevant Microsoft sections read through 2026-10-05T19:04:35Z; no update dates displayed. The then-current body had sixteen author synthetic decisions and six additional distinct-checker boundaries under the same controller; no real export/restoration or independent formal review was established. Recheck before use, after client/configuration/source changes and by 2026-11-05T19:04:35Z. Follow the email standard [current article]. Feedback should identify the public disputed branch.
This retrospective restructuring preserves earlier source clocks and refresh deadlines. The publication body check has its own scope; it does not establish live service outcomes or freshly verify every inherited claim.