Table of Contents

Enum MailFolderRunOutcome

Namespace
MailFathom.Application.Synchronization.Administration
Assembly
MailFathom.Application.dll

How one folder's turn through a synchronization run ended.

public enum MailFolderRunOutcome

Fields

AliasAmbiguous = 2

Several advertised folders matched the alias, so the folder was not synchronized until a remote path says which one it means.

AliasUnresolved = 1

The mail server advertised no folder matching the alias, so the folder was not synchronized.

DeferredAfterConcurrencyConflict = 3

Another writer moved the folder's progress while the run was deciding from it, so the run gave the folder up to the next one.

DeferredAfterMailServerUnavailable = 4

The mail server did not serve the folder within the account's resilience budget.

InterruptedByShutdown = 6

The host began shutting down while the folder was running, so the run ended without finishing.

Synchronized = 0

The run reached the folder the alias is bound to and committed what it fetched.

UnexpectedFailure = 5

The folder's run ended in a way nothing here classifies, which is a defect rather than a condition to wait out.

Remarks

It is the classification a failing folder is read by, and it is deliberately a closed set of names rather than anything the failure itself carried. An administrative surface must publish neither an exception message nor a remote folder path, and what an operator acts on is which of these happened: two of them are corrected by editing a folder mapping, two are waited out, and one is a defect to report.

The members mirror the branches the supervisor already separates when it logs a folder, so a value here and the line in a log describe the same event rather than two classifications that happen to agree.