Skip to main content

E-mail error codes (mpbx-email)

Raised by the e-mail provider settings (/api/v1/email/provider), the test mail, and every feature that sends mail through a company's provider (onboarding invitations, voicemail to e-mail; W4-AUTH-01). Messages never contain an API key, a password, a recipient address or the body of a mail; a provider's failure is reported by its HTTP status or SMTP reply code only. Guide: E-mail.

CodeKindMeaningWhat to do
MPBX-EMAIL-CONFIG-INVALIDinvalid_argumentA provider setting is missing or malformed (the message names the field): from is not one mail address, the SMTP host is not a host name or resolves to a private, loopback or reserved address, security is not starttls or tls, a password without a user name, an AWS region or access key id that does not look like one, a Mailgun domain that is not a DNS name, or an API provider without its key.Fix the named field. Private SMTP relays need the operator setting [email] allow_private_smtp = true.
MPBX-EMAIL-NOT-CONFIGUREDunavailableNeither the company nor the install has an e-mail provider, so nothing can be sent (an invitation is not created).Configure the company's provider, or the operator's [email.smtp].
MPBX-EMAIL-REJECTEDinvalid_argumentThe provider refused the mail for good: the recipient, the sender (not verified at the provider), the credentials (HTTP 401/403, SMTP 535) or the message. Not retried.Check the provider's sender verification and the credentials; then send the test mail again.
MPBX-EMAIL-UNAVAILABLEunavailableThe provider could not be reached, timed out, or answered with a temporary failure (HTTP 408, 429 or 5xx; SMTP 4xx).Try again later; check the provider's status page and the server's outbound connectivity.
MPBX-EMAIL-SECRET-UNREADABLEconfigThe stored password or API key cannot be opened with this install's master key (a restored database with another master key, or a damaged row).Enter the secret again in the provider settings.