Message store unavailable

store.unavailable · HTTP 503

What it means

Message storage could not be reached, so message bodies, raw sources and attachments cannot be read for now; where it can, the problem's message field still carries the message's index fields. Lists, search and wait keep working, except a wait that needs the body: one with includeBody=true, or with a pattern the subject does not match. Deleting an inbox or purging a tag also answers this when an inbox could not be removed yet because mail kept arriving while it ran, with the counts so far. Injecting a message answers this when the message could not be stored, and then nothing was stored.

What to do

Retry after a short while. An injection can be sent again as it was: its Message-ID makes the retry safe. After a deletion or a purge, the inboxes already refuse new mail and the rest is removed automatically; repeat the call to finish it now.

Every error the API returns is a JSON problem (RFC 9457) whose code names it and whose type links to its page here. See the docs for how the API works.