Mail originals and attachment evidence
Estate preserves the canonical RFC822 message originals and attachment bytes. Toolora stores a bounded searchable projection and, for enabled document intake, verified encrypted working copies. These layers have separate identities and coverage. A listed message or attachment descriptor does not prove its bytes are available for retrieval.
Source identity and copies
Section titled “Source identity and copies”| Identity | Meaning | It does not establish |
|---|---|---|
| Archive account, cell and connection | Attested source mapped to one Toolora company/mailbox binding | Permission for every company member to read it |
source_ref and original version reference |
Source occurrence and version projected into Toolora | That a subject or Message-ID is globally unique |
| RFC822 hash | Expected original content | That the message’s supplier claim is correct |
| Attachment ordinal and SHA-256 | One part occurrence within a source version, plus its expected bytes | That equal bytes from separate occurrences are the same candidate |
Verified mail_original_copies row |
Intake’s protected local copy for the matching source/version | A universal archive completeness or retention guarantee |
Archive projection upserts by company and source reference. Intake attachment occurrences retain original version and ordinal; source hashes support later verification and review. A filename is presentation, not identity. Reindexing must not replace confirmed interpretation merely because the same occurrence reappears. Document intake owns candidate versions and decisions.
flowchart LR Archive[Estate original and coverage] --> Projection[Toolora mailbox projection] Archive --> Verify[Authorized hash-checked retrieval] Verify --> Reader[Current mailbox reader] Verify --> Copy[Enabled intake encrypted copy] Copy --> Candidate[Versioned attachment candidate] Candidate --> Review[Human classification and routing]
Reader and retrieval paths
Section titled “Reader and retrieval paths”Mailbox reads require staff mail capability, an enabled/read-enabled binding and current company-administrator reader membership. Object workspaces add their customer/opportunity/project read check. A target link does not grant mailbox access. Mail integration owns setup and reader policy.
The archive client resolves an original-version reference to a read reference and then fetches bounded RFC822 bytes without following redirects. The reviewed client limits originals to 52,428,800 bytes and attachment retrieval to 25,000,000 bytes. Mailbox detail uses indexed body text when present; if it is missing, it can verify the fetched original against the expected MIME hash and extract readable text. Search still uses the indexed projection.
Attachment retrieval binds company, mailbox, message and ordinal, refuses source tombstones and checks the attachment hash/MIME against the original. Safe PDF/image previews use sandboxed, no-store responses; other supported downloads use an attachment disposition. Remote email images and scripts are not fetched. Intake and MCP original reads have their own capability, source and verified-copy checks; they are not an alternate way around the mailbox reader boundary.
Coverage and freshness
Section titled “Coverage and freshness”| Observation | Supported conclusion | Reader action |
|---|---|---|
| Metadata exists; original or attachment coverage is missing | A source occurrence is known, with incomplete bytes | Show the gap; do not substitute an invented empty file. |
| Bounded page stops before the generation ends | This projection pass is partial | Continue the returned checkpoint under the source contract. |
| Generation or item coverage is incomplete | Completeness is not established | The projection keeps the previous durable sequence eligible for retry. |
| Verified bytes match the expected hash | Retrieved bytes correspond to that source/version | Keep business interpretation and approval separate. |
| A source tombstone is synchronized | The projected source is deleted | Stop ordinary reads of that projection; do not promise recall of prior downloads. |
sync_archive_projection combines generation coverage, per-item metadata/original/
attachment flags, known gaps and page completion. A successful HTTP response alone
cannot advance an incomplete generation as though it were complete. Missing email
dates stay missing; archive observation time is not an email sent date.
Recovery and evidence
Section titled “Recovery and evidence”For synthetic Message A, a visible attachment with no verified source hash is unavailable, even when another message has an identical filename. A foreign-company binding or unauthorized reader must be refused before byte retrieval. When coverage is incomplete, inspect binding identity, source status and the named error code; do not add a new mailbox connection, copy private originals into fixtures or clear checkpoints to manufacture completeness.
Estate’s recorded source policy and lifecycle signal govern source retention. Toolora does not define an additional universal expiry schedule here. The intake copy protects working bytes, while Storage owns local object and downloaded-copy limits. Mail-body, attachment, client and policy tests use synthetic content and substituted archive responses; the delivery PR states which were executed. This review makes no new claim about a real mailbox’s current original coverage or a combined archive restore.