Enum EmailBodyAvailability

Namespace

MailFathom.Application.EmailContent.Rendering

Assembly

MailFathom.Application.dll

States whether a reader was given the message body, or why it could not be.

public enum EmailBodyAvailability

Fields

EncryptedNotReadableLocally = 1

The body arrived inside a cryptographic envelope, so nothing here can read it.

Decryption is out of scope; the state exists so an unreadable body is explicit rather than an empty one.

NotStoredAwaitingStorageHeadroom = 3

Local content storage was at its configured ceiling when the message arrived, so its content is not stored yet.

This is not a defect and schedules no repair either, and unlike the state above it is temporary: a later synchronization run fetches the content as soon as the ceiling has room, and the same read then returns the body.

NotStoredExceededSizeLimit = 2

The message exceeded the configured raw MIME size limit, so its content was never stored locally.

This is not a defect and schedules no repair: synchronization recorded the occurrence and deliberately stored no content for it, and requesting repair would ask a later run to store what the same limit will refuse again.

Readable = 0

The body was read from the stored message, and an empty one means the message displayed nothing.

Remarks

The three unreadable cases stay apart because a caller acts on each differently and none of them is an empty message. One is mail this deployment holds and cannot decrypt; one is mail whose bytes a configured limit will refuse on every run, so asking again is pointless; and one is mail whose bytes are simply not stored yet, so asking again once storage has room is exactly the right thing to do.