Proving an address belongs to you, and Quavern's ability to send to it at all.
Find your code below — there are 7 of them. The digit between the letters and the dash says who can act on it: 1 is something you can change, 2 and 9 are Quavern's to fix, 3, 4 and 5 are decisions about access, 6 and 7 mean the service is in maintenance or has moved, and 8 points at the device or the network. MAIL uses 1, 2, 3. The shape of a code is explained in How to read a Quavern support code.
Class 1 — Your request or your action
Check what you sent and the state of the account: the request itself, a quota, or the object it names. Correcting that and trying again is normally the whole fix.
MAIL1-1400 — invalid_email_verification
What it means. Quavern refused the e-mail verification link: what arrived is not in the form this route accepts.
MAIL1-2400 — email_verification_expired
What it means. The e-mail verification link was genuine, but its lifetime has run out.
What to do. Start the step again to obtain a fresh value. Do not resend the old one.
MAIL1-3409 — email_already_verified
What it means. The e-mail address is already in the state the request asked for, so Quavern did nothing rather than do it twice.
What to do. Nothing is broken. Read the current state before repeating the step.
MAIL1-4429 — email_resend_throttled
What it means. Requests arrived faster than Quavern accepts here. There is nothing wrong with what you sent.
What to do. Wait, then try again more slowly. Honour the Retry-After header when the response carries one.
Class 2 — Quavern's server or one of its dependencies
Nothing you did caused it. Wait a moment and try again. If it keeps happening, send support the code and the time — that is what lets the incident be found in the logs.
MAIL2-1503 — email_delivery_unconfigured
What it means. E-mail delivery has not been given the configuration this needs on this deployment, so the feature is switched off rather than half working.
What to do. Nothing on your side fixes this. Tell support, with the code and the time.
MAIL2-2502 — email_delivery_failed
What it means. E-mail delivery failed. The failure is on Quavern's side, not in what you sent.
Class 3 — Authentication, authorisation or security
Sign in again, or ask whoever administers your organisation for the access this needs. Support will never work around an access control on your behalf.
MAIL3-1403 — email_verification_required
What it means. The request cannot go ahead without a verified e-mail address.
Still stuck
Write to [email protected] with the code, the reason, the time with its time zone, and the route you called. Never send a password, a token, an API key or full card details — support will never ask for any of them.
Quavern help reference: support-codes-mail/en