Class AttachmentDownload

Namespace

MailFathom.Application.EmailContent.Attachments

Assembly

MailFathom.Application.dll

How an attachment's content is reachable from one read, or why it is not reachable from this one.

public sealed record AttachmentDownload : IEquatable<AttachmentDownload>

Inheritance

object

AttachmentDownload

Implements

IEquatable<AttachmentDownload>

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

A read never carries a file's octets. What it can carry is a capability to fetch them, and this is either that capability or the reason none was minted. The distinction is the whole point: describing an attachment costs nothing and happens on every read, while minting a link is what a caller asks for and what a deployment has to be configured to do.

The link is a bearer capability rather than mail content, and it is treated as the more sensitive of the two: mail content requires the reader to already hold it, and this obtains some for whoever holds the URL.

Properties

Availability

Gets whether a link was minted, and why it was not when it was not.

Link

Gets the minted link, which is present for Issued and absent otherwise.

NotRequested

Gets the download of an attachment nothing asked to fetch.

Unavailable

Gets the download of an attachment this deployment can mint no link for.

Methods

Issued(AttachmentDownloadLink)

Carries the link a read minted for one attachment.