Creating a credential
Create and manage SMTP credentials in the dashboard under SMTP credentials. Each credential belongs to a single domain.Authenticating
Most clients ask for a username and password and handle theAUTH exchange for you. Provide:
- Username. Your SMTP credential’s username, followed by
@and the domain it is bound to, for example[email protected]. - Password. The credential’s secret.
--ssl-reqd makes STARTTLS mandatory, so curl aborts rather than falling back to plaintext. Drop the @example.com from --user and the same command returns 535 5.7.8 AUTH invalid.
Every authentication failure returns the same reply, 535 5.7.8 AUTH invalid. A wrong password, an unknown user, a malformed username, an inactive domain or organization, and a connection from outside the credential’s source-IP allowlist (when you configured one) are deliberately indistinguishable, so the reply never confirms which part was wrong. Check the credential and its configuration rather than parsing the reply.
The password is not your API key: API keys authenticate the REST API, and SMTP
uses a separate credential.
Always authenticate over a TLS-protected connection (STARTTLS on port 587) so the credentials are never sent in the clear. See Connection.