Class OutgoingMailReader
- Namespace
- MailFathom.Application.Mail.Delivery.Tracking
- Assembly
- MailFathom.Application.dll
Reads back one send the caller asked for, so an asynchronous result becomes an answerable question.
public sealed class OutgoingMailReader
- Inheritance
-
OutgoingMailReader
- Inherited Members
Remarks
Queueing is what a send is, so something has to say what became of what was queued. Without this a caller holds an identifier and no way to learn whether the message left, and the worst thing available to an agent in that position is to send again — which is why this exists beside the sending tools rather than as a convenience beyond them.
It reads one record and never a set. There is no listing here and none is coming: a call names the record it already holds an identifier for, so the answer is bounded at one and nothing on this path can be walked into an export of what a mailbox has sent.
What a caller may read is what that caller queued. The record remembers the principal the outbox admitted it under, and a record admitted under any other answers exactly as a record that does not exist — including a record a rule queued, which no caller asked for at all and which the origin check refuses on its own even where a credential happens to be named as this process is.
Constructors
- OutgoingMailReader(IOutgoingEmailStore, AccessAuthorization)
Reads back one send the caller asked for, so an asynchronous result becomes an answerable question.
Methods
- ReadAsync(OutgoingEmailId, CancellationToken)
Reads back the send one identifier names, for the caller that asked for it.