Skip to main content

Search OfficeIMO

Enter a topic, API type, or PowerShell command.

Documentation Search all OfficeIMO/
Class

ReaderEmailStoreOptions

OfficeIMO.Reader.Email

Namespace
OfficeIMO.Reader.Email
Assembly
OfficeIMO.Reader.Email
Source revision
ba882f6b0d07 with working tree changes
Modifiers
sealed

Options for projecting email stores through OfficeIMO.Reader.

Inheritance

  • object
  • ReaderEmailStoreOptions

Usage

Explore 6 API references to this type

This type appears in these public API surfaces even when no hand-authored example is attached directly to the page.

Returned or exposed by 1

Accepted by parameters 5

Constructors

public ReaderEmailStoreOptions() #

Properties

public EmailConcealedTextPolicy ConcealedTextPolicy { get; set; } #

Controls concealed HTML in derived item content. Selected bodies are inspected under either policy.

public EmailStoreReaderOptions? StoreOptions { get; set; } #

Gets or sets bounded store-reader options. Registrations capture a defensive copy. A Reader-level ReaderOptions.MaxInputBytes can narrow, but never widen, this limit.

public EmailStoreQuery? Query { get; set; } #

Optional selective summary query applied before full item projection. This is the preferred way to ingest a narrow slice of a very large PST or OST.

public EmailStoreItemReadOptions? ItemReadOptions { get; set; } #

Selective item parts projected before Reader chunking. Null uses the full semantic item profile.

public bool StreamAttachmentContent { get; set; } #

Whether store attachment payloads use session-bound streams instead of resident byte arrays. Enabled by default for bounded large-store ingestion.

public int MaxItems { get; set; } #

Maximum matching items fully projected into one Reader result. Default: 1,000.

public bool ContinueOnItemError { get; set; } #

Whether a corrupt or over-limit item is diagnosed and skipped instead of aborting the store.

public bool ComputeSourceHash { get; set; } #

Whether Reader hashes the complete source store. Disabled by default because hashing a huge PST/OST forces a full sequential read even when parsing selected items is random-access and bounded. Chunk hashes still follow ReaderOptions.ComputeHashes.