Property IsUnknownPlacementSettledBySourceRemoval

Namespace

MailFathom.Domain.Mutations

Assembly

MailFathom.Domain.dll

IsUnknownPlacementSettledBySourceRemoval

Reports whether an unacknowledged placement has since been settled by the source occurrence leaving its folder.

public bool IsUnknownPlacementSettledBySourceRemoval { get; }

Property Value

bool

Remarks

It answers for one shape only, and the narrowness is the point. A relocation carried by MOVE removes the source as part of the same command, so a source that has gone is the server's own statement that the command ran — a fact about an occurrence the record names exactly, rather than a guess about which message in the destination folder is the one that was placed. A copy and a fallback relocation both leave the source where it was, so its presence says nothing about either and neither is settled here.

The one way this reads wrong is an owner who deleted the source message themselves between the command going out and the folder being read again, which would credit the move for a disappearance it did not cause. The mutation is completed anyway, deliberately: the email has left the source folder either way, nothing is duplicated by saying so, and reissuing a MOVE against a UID the folder no longer holds could only fail. It is the same direction AccountsForRemovalOf(EmailOccurrenceId) already takes for the same reason.