# Fix "550 Sender verify failed"
Source: https://docs.webgee.com/en/email/how-to-solve-550-sender-verify-failed-error-message





`550 Sender verify failed` is the receiving server refusing your message because
it could not confirm the **From** address is real. Applies to shared, reseller
and cPanel hosting.

There are two causes, and they are checked in different places.

## Cause 1: the sending address does not exist [#cause-1-the-sending-address-does-not-exist]

The most common case. Something is sending as `you@example.com`, but no mailbox
by that name exists in cPanel — often because the address was only ever set up
inside a mail app, or a contact form was configured with an address nobody
created.

1. Log in to cPanel.
2. Open **Email Accounts**.
3. Confirm the address you are sending from is listed.

If it is not there, create it. If it is there, check that your mail app is
authenticating with that exact address as the username and the correct mailbox
password — see
[Fix "550 Please turn on SMTP Authentication"](/en/email/understanding-and-resolving-the-550-please-turn-on-smtp-authentication-error).

## Cause 2: email routing is set the wrong way [#cause-2-email-routing-is-set-the-wrong-way]

This is what catches people out after moving mail to Google Workspace,
Microsoft 365 or any other external provider.

Changing the MX records at your registrar tells the *outside world* where to
deliver mail. It does not tell *your own server*. Until you also change email
routing in cPanel, the server assumes it still handles mail for the domain,
looks for a local mailbox that no longer exists, and rejects the message.

1. Log in to cPanel.
2. Open **Zone Editor**, select the domain, then **Manage**.
3. Find the **Email Routing** configuration.
4. Set it to **Remote Mail Exchanger**.

<img alt="The Email Routing configuration in cPanel, with Remote Mail Exchanger selected" src="__img0" />

If mail for the domain *is* handled by WebGee, this must be **Local Mail
Exchanger** instead. Getting it backwards produces the same error from the
opposite direction.

See [Configure email routing in cPanel](/en/email/how-do-i-configure-my-email-routing-in-cpanel)
for the full procedure.

<Callout type="warn">
  Addon and parked domains each have their own routing setting and do not
  inherit it from the main domain. If the error affects one domain on an account
  and not the others, this is almost always why.
</Callout>

## Verify [#verify]

Send a test message from the affected address and confirm it is accepted. If it
still fails, check the full rejection text — a different `550` code points
somewhere else entirely. See
[Read email headers](/en/email/how-to-obtain-email-headers-a-step-by-step-guide).

## Related [#related]

* [Configure email routing in cPanel](/en/email/how-do-i-configure-my-email-routing-in-cpanel)
* [Fix "550 Please turn on SMTP Authentication"](/en/email/understanding-and-resolving-the-550-please-turn-on-smtp-authentication-error)
* [Create email accounts in cPanel](/en/email/how-to-create-email-accounts-in-cpanel)