Cannot send email: SMTP authentication failed

For hosting customers · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Websites (PHP mail)
  5. Still not working?

To send mail through this server, a mail app or website must sign in (SMTP authentication) with the full email address and the mailbox password, on port 465 or 587. Most sending problems are one of these settings.

Symptoms

  • The mail app says "SMTP authentication failed", "535 5.7.8 Authentication failed", "Cannot send message" or "The server rejected your username or password".
  • Sending times out or the connection is refused, while receiving works.
  • The message bounces with an error from this server (see the codes below).

Causes

Most likely first:

  1. Wrong username or password — the username must be the full email address; the password is the mailbox's, not the control panel's.
  2. Wrong port or encryption — port 25 is used, or the encryption does not match the port.
  3. Your network blocks the port (some internet providers and office networks block outgoing mail ports).
  4. Your address was banned after several failed sign-ins.
  5. The message was refused by a rule of this server (other domain in From, hourly limit, spam score).

Fix

1. Username and password

  1. Open Email Accounts (section Email). Under Mail client settings the page shows the exact settings.
  2. Username: the full email address, for example [email protected].
  3. If you are not sure of the password, click Password next to the mailbox, enter a new one and click Change. Then enter it in the app.

Try signing in to Webmail (Open Webmail) with the same address and password. If webmail works, the password is right and the problem is in the app's settings.

2. Port and encryption

Outgoing (SMTP), with sign-in required:

PortEncryption
465SSL/TLS
587STARTTLS

Use the server name shown under Mail client settings: mail. plus your domain once your website has its certificate, otherwise the server's own name. Another name gives certificate warnings. Outlook and Thunderbird find these settings themselves when you enter only the address and password.

3. The network blocks the port

Try the other port (465 instead of 587, or the other way round), or another network such as mobile data. If neither works anywhere, contact your host.

4. Banned after failed sign-ins

After 6 failed sign-ins within 10 minutes, the server bans the address for one hour for mail sign-in (all mail apps on that network). Wait an hour, or ask your host to lift the ban (Firewall → Unban). Fix the password in every device first, or an old phone will cause the ban again. See My IP is blocked.

5. The server refused the message

Read the bounce or the error in the app:

  • 550 5.7.1 This account cannot send email as …: use an address of your own domains. — the From address belongs to another hosting account on this server. Send from your own domain.
  • 451 4.7.1 This account reached its limit of … emails per hour. — see hourly sending limit.
  • 554 5.7.1 Spam message rejected — the content was scored as spam. Change the content and try again.

Delivery reports (on Email Accounts, Direction Outgoing) shows each attempt and its result.

Websites (PHP mail)

Websites on this server send through your account automatically with PHP mail(); no SMTP settings are needed. If you prefer an SMTP plugin (for example in WordPress), give it the same settings as a mail app: the server name from Mail client settings, port 587 or 465, the full email address and its password.

Still not working?

Contact your host through Support with the exact error message, the time, and the address you send from.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.