Property Attachments

Namespace

MailFathom.Application.Emails.GetEmailContent

Assembly

MailFathom.Application.dll

Attachments

Gets one entry per attachment when the request asked to describe them, and never any of their bytes.

public IReadOnlyList<ExtractedEmailAttachment>? Attachments { get; init; }

Property Value

IReadOnlyList<ExtractedEmailAttachment>

Remarks

It is null when the request did not ask, which is not the same finding as an empty list: a file name is sender-chosen mail content and frequently the most identifying string a message carries, so a read that only wanted the body publishes none. AttachmentSummary still states how many there are, so a caller can tell that asking again would describe something.

The list is re-derived rather than stored, because file names are mail content that the row deliberately does not keep. Deriving it during the parse that produces the body costs nothing extra and guarantees it describes the message it was read from.

It is empty when the message's raw MIME was never stored locally, which NotStoredExceededSizeLimit on the body states. Inline resources and cryptographic parts never appear here; they are counted in AttachmentSummary instead.