Enum OutgoingMailFilingOutcome

Namespace

MailFathom.Application.Mail.Delivery.Filing

Assembly

MailFathom.Application.dll

States how one attempt to file a copy of an outgoing message ended.

public enum OutgoingMailFilingOutcome

Fields

AlreadyFiled = 1

A copy was already in the folder from an earlier attempt, so nothing was appended.

DestinationUnavailable = 3

There is no folder to put the copy into, and the account's folder mapping is what changes that.

Failed = 5

The attempt failed before anything reached the folder, and may be attempted again on its own.

Filed = 0

The folder accepted the copy.

NotRequested = 2

The account asked for no copy in this place, so nothing was attempted.

It covers an account that switched the sent copy off and a deployment that mapped no folder to the outbox role, which are the same thing to read: this deployment does not want a copy here, and that is not a failure.

OutcomeUnknown = 4

The append went out and the server's answer never came back, so nobody can say whether the copy is there.

The one outcome that is never attempted again. A second append is a second message in the owner's folder, and nothing the folder shows afterwards tells the two apart.

Withdrawn = 6

The copy has been taken back out of the folder, or was already gone from it.

It is its own member rather than Filed read backwards, because both endings are counted: a dashboard reading how many copies this deployment put into somebody's mailbox must not have withdrawals added into that number.

Remarks

None of these is a delivery outcome, and that separation is the point. A message is delivered or it is not; where a copy of it ended up is a second account of the same message, and every member here leaves a completed delivery exactly as completed as it was.