Back to app

Troubleshooting SMTP Errors

Decode the error messages your mail server returns and fix the underlying cause.

When a test or a send fails, Vecta stores the server's exact response on the SMTP config and on the individual send record. That text is the fastest route to the cause.

Authentication errors

MessageCauseFix
535 Authentication failedWrong password, or provider requires an app passwordGenerate an app password (Gmail, Outlook) and use that
534 / 5.7.9 application-specific password required2FA is onCreate an app password
Username and Password not acceptedUsername isn't the full addressUse the complete email address

Connection errors

MessageCauseFix
Connection timeoutWrong host/port, or outbound SMTP blockedVerify host spelling; try 587, then 465
ECONNREFUSEDNothing listening on that portWrong port for this provider
self-signed certificate / hostname mismatchHost doesn't match the certificateUse the exact host your provider documents

Rejection errors

MessageCauseFix
550 relay access deniedFrom address isn't owned by the authenticated mailboxSet From to your real address
553 sender address rejectedSame as above, phrased differentlyMatch From to the mailbox
552 message too largeBody exceeds the server limitShorten the email; avoid embedding images
421 too many messagesYou're sending too fastLower your per-minute and per-second caps

These never suppress your contacts

Everything above is a problem on your side, so Vecta records the send as failed but leaves the contact untouched. Only a genuine recipient rejection marks someone as bounced.

A repeatable checklist

  1. 1Open the SMTP config and read the stored error text.
  2. 2Press Test to reproduce it on demand.
  3. 3Confirm the username is the full email address.
  4. 4Try port 587, then 465.
  5. 5Confirm the From address matches the mailbox.
  6. 6If the provider uses 2FA, regenerate the app password.

Did this help?

Related articles