Provider directory
Identify the actual service, available files and relevant period. A product name alone does not establish an acquisition route.
Original content baseline 6 November 2026 · Content revision 0.3
Capability status: requires assessment. These are enquiry categories. D3 has not confirmed every provider or historical method in this review build.
Other providers
Account material, supplied exports, local copies or backups for assessment.
Limit: Account history, access status and surviving source format must be established; a provider name is not a recovery commitment.
Discuss the available sourceOther providers
Supplied messages, authorised account material and older client stores.
Limit: Historical account changes and local export provenance need assessment before completeness can be evaluated.
Discuss the available sourceOther providers
Available user or organisation-provided exports and administrator material.
Limit: Organisation access, account edition and the actual export scope must be confirmed.
Discuss the available sourceOther providers
Authorised account material, messages and existing local stores.
Limit: Aliases, domains and client copies must be reconciled to the relevant account and dates.
Discuss the available sourceEncrypted services
Authorised exports or existing local copies; Proton documents export routes.
Limit: A supported export route does not establish deleted-data recovery or any ability to defeat encryption.
Read Proton export guidance (external)
Discuss the available sourceEncrypted services
Material already supplied by an authorised account holder and any feasible export route.
Limit: Access, keys, client version and export coverage require assessment. Encryption bypass is not offered or implied.
Discuss the available sourceRegional and ISP mail
Supplied messages, account exports where feasible and existing client material.
Limit: Account access, authorisation, language and collection restrictions must be established for the particular matter.
Discuss the available sourceRegional and ISP mail
Organisation-supplied messages and authorised administrative material for assessment.
Limit: Consumer QQ access and enterprise administration must not be treated as equivalent evidence routes.
Discuss the available sourceRegional and ISP mail
Available authorised messages, exports and local client stores.
Limit: The precise service, account status and source history require confirmation before collection is scoped.
Discuss the available sourceRegional and ISP mail
Organisation-provided material and feasible authorised account sources.
Limit: Administrator permissions, service variant and retained history must be checked rather than assumed.
Discuss the available sourceRegional and ISP mail
Supplied historical messages, backups and client stores, together with accessible account material.
Limit: An older backup may hold a different population from the current account; provenance and coverage require reconciliation.
Discuss the available sourceSelf-hosted and legacy
Supplied mailbox material, server stores, archives and backups for assessment.
Limit: Edition, version, hosting arrangement and export format must be identified before an examination route is confirmed.
Read self-hosted mail guidance
Discuss the available sourceSelf-hosted and legacy
Underlying mailbox service and relevant webmail configuration or artefacts.
Limit: Roundcube is a webmail client; its web server cannot be assumed to contain a complete mailbox or history.
Read self-hosted mail guidance
Discuss the available sourceArchives and gateways
Authorised archive exports or gateway records supplied for the agreed matter.
Limit: Actual product configuration, retained scope and administrator permissions determine what may be available.
View the evidence source matrix
Discuss the available sourceArchives and gateways
Available archive, journal or gateway records from the specific deployment.
Limit: A gateway event is different from preserved message content; the deployed product and source must be identified.
View the evidence source matrix
Discuss the available sourceArchives and gateways
Existing archive exports and associated metadata for assessment.
Limit: Archive scope, export transformations and links to original custodians must be documented.
View the evidence source matrix
Discuss the available sourceArchives and gateways
Supplied archive material and any available acquisition records.
Limit: An archive's existence does not establish that every mailbox or date range was captured.
View the evidence source matrix
Discuss the available sourceArchives and gateways
Records from the identified archive, backup or gateway product.
Limit: The product family contains different source types; a brand name alone does not define content or retention.
View the evidence source matrix
Discuss the available sourceSelf-hosted and legacy
Supplied NSF databases, exports and backups for format and access assessment.
Limit: Version, database design, encryption and authorised credentials may affect interpretation and accessibility.
Discuss the available sourceSelf-hosted and legacy
Supplied mailbox, archive or historical backup material.
Limit: Legacy version, available software and export provenance must be established before examination is agreed.
Discuss the available sourceSelf-hosted and legacy
Available server stores, exports and backup material for assessment.
Limit: The storage layout, version and backup completeness require an environment-specific review.
Discuss the available sourceSelf-hosted and legacy
Supplied messages, server stores and relevant logs or backups.
Limit: Collection scope must distinguish message content from transport and account-activity records.
Discuss the available sourceStart with the question
A brief account of the issue, the available sources and the relevant dates is enough to begin.