START HERE · Published 2026-10-06 · Updated 2026-10-09 · SecureSMTP
Support
How to reach us and what to include so we can help quickly.
Contact
- Open a ticket on the support page, or from Support in your dashboard. You get a ticket number and a link to follow it.
- Or email [email protected]; that opens a ticket too. Reply to any of our emails to add to your ticket.
- Live service status: securessmtp.com/status.
What to include
- The site’s domain (never the API key).
- For a sending problem: the
message_idfrom the API response, or the recipient and the time. - For an API error: the endpoint, the HTTP status and the full response body.
- For the WordPress plugin: the plugin version (shown on its Settings page) and what the Test connection button says.
Before you write
- Look the email up in the email log — the reason for a bounce is usually there.
- Look the error up in the error catalogue.
- Check that the address is not on your suppression list.
Questions we get most
The email log says sent, but the email did not arrive
sent means we accepted the email and handed it over for delivery; delivered means the receiving server accepted it. After that, the receiver decides where it goes, so check the spam or junk folder first. If the log shows bounced, the reason from the receiving server is next to it. The email log guide lists every status.
SMTP login fails
Use host smtp.securessmtp.com, port 587 with STARTTLS (or 465 with SSL), username securessmtp and the site’s API key as the password. A key that was rotated stops working at once. See the SMTP guide.
My sending domain will not verify
Check that the DKIM record is on the exact host name shown in the dashboard. Many DNS panels add your domain to the name for you, so entering the full name doubles it. New records can take a while to appear. See Domains and DNS.
Nothing sends from a new account
New accounts confirm their email address before their sites can send. Open the confirmation email we sent when you signed up, or ask for a new one from the dashboard.