550 Sender verify failed error: how to fix it

Introduction

The 550 Sender verify failed error appears when a mail server rejects a message because it cannot verify the sender address. In practice, this means the receiving server is trying to confirm that the sending account exists or that the domain is configured correctly, but that check fails.

It may happen when sending messages from a hosting email account, a web form, an application or even when replying to email. In most cases, the fix is to review the mailbox, the SMTP settings, the DNS records and the email routing in the hosting panel.

Steps to fix the error

1. Review the full error message

   Before changing anything, open the complete bounce or error notice. It often looks like this:

   550 Sender verify failed

   You may also see messages such as:

   The mail server could not verify the sender address

   or:

   Sender address rejected: undeliverable address

   Pay close attention to:

   • the email address that is trying to send
   • the sender domain
   • the server rejecting the message
   • whether the error happens from Webmail, Outlook, Thunderbird, a website or an application

2. Make sure the sender mailbox exists

   One of the most common causes is trying to send from an address that does not actually exist inside the hosting account.

   If your website or mail client sends as:

   contact@yourdomain.com

   you need to confirm that this mailbox has been created in the panel.

   In DirectAdmin:

   1. Open DirectAdmin.
   2. Go to E-mail Manager.
   3. Open E-mail Accounts.
   4. Check whether the mailbox exists.
   5. If it does not exist, create it with the correct name.

   In cPanel:

   1. Open cPanel.
   2. Go to the email section.
   3. Open Email Accounts.
   4. Look for the sender mailbox.
   5. If it is missing, create it.

3. Verify that the domain is active and points to the correct hosting

   The server may reject the message if the sender domain does not resolve correctly or is not associated with the right hosting environment.

   Review that:

   • the domain is registered and active
   • the nameservers point correctly
   • the DNS zone exists on the server
   • the MX records match the mail service you use
   • the domain is not expired or suspended

   If you use the email service included with your hosting, the normal setup is to have the DNS and MX records pointing to the corresponding hosting server. If you use an external email provider, the MX records must point there instead of the local hosting server, unless mail is handled locally.

4. Review the domain email routing

   Email routing tells the server whether it should handle email locally or pass it to an external provider. If this is set incorrectly, the server may try to verify the sender in the wrong place.

   In cPanel:

   1. Open cPanel.
   2. Look for Email Routing.
   3. Select the domain.
   4. Choose the correct option:
      • Local Mail Exchanger if email is handled inside the hosting account
      • Remote Mail Exchanger if email is handled by another provider
      • Automatically Detect Configuration if you want the panel to make an initial detection

   In DirectAdmin, this setting may appear under the domain DNS or email management area. If your email is hosted elsewhere, the important point is to avoid local delivery conflicts and make sure the external MX records are correct.

5. Confirm that the web form uses a valid sender

   This error is very common in contact forms, online stores, WordPress sites and other applications that try to send mail using a made-up or nonexistent sender address.

   Avoid sender addresses such as:

   user@gmail.com
   client@hotmail.com
   no-reply@domain-that-does-not-exist.com

   A better approach is to use a real mailbox on your own domain, for example:

   no-reply@yourdomain.com
   contact@yourdomain.com
   web@yourdomain.com

   Then use the visitor email in Reply-To, for example:

   From: no-reply@yourdomain.com
   Reply-To: customer-email@example.com

6. Use authenticated SMTP instead of mail()

   Many older websites still use the PHP mail() function. It can work, but it does not always authenticate the sender properly and may trigger delivery failures.

   To improve reliability, configure your website or application to send through authenticated SMTP. You will usually need:

   • SMTP server
   • full email username, such as contact@yourdomain.com
   • mailbox password
   • SMTP port
   • SSL or TLS encryption

   In WordPress, for example, this is often configured with an SMTP plugin and a real mailbox created in the hosting account.

7. Review SPF, DKIM and DMARC records

   Although this error is not always caused directly by SPF, DKIM or DMARC, incomplete mail authentication increases the chance of rejection and hurts the domain reputation.

   Make sure the domain has:

   • SPF to authorize which servers may send email for the domain
   • DKIM to digitally sign messages
   • DMARC to define what should happen when SPF or DKIM fail

   In DirectAdmin and cPanel, these records are usually reviewed from the DNS or email authentication sections.

8. Check whether the account or domain has restrictions

   The server may also reject messages if it detects other issues. Review whether:

   • the hosting account is active
   • the domain is not suspended
   • the mailbox has not exceeded its quota
   • the server has not reached sending limits
   • the SMTP password is correct
   • there are no scripts or forms sending unwanted email

Useful tips

1. Always use a real sender mailbox

   Do not configure forms or applications to send from nonexistent addresses. Create a mailbox such as no-reply@yourdomain.com and use it for authenticated sending.

2. Understand the difference between From and Reply-To

   The From field should be a valid address on the domain. Reply-To may contain the customer or visitor email address.

3. Do not mix local and external mail without reviewing MX

   If the website is hosted in one place but email is handled elsewhere, make sure the MX records and routing match that setup.

4. Wait for propagation after DNS changes

   DNS changes can take time to fully propagate. During that period, some servers may still see the previous configuration.

FAQ

What does 550 Sender verify failed mean

It means the mail server could not verify the sender address. The mailbox may not exist, the domain may not resolve correctly, the mail setup may be wrong or the sender may not be authenticated.

Is the problem in my hosting or on the recipient server

It can be on either side. If the sender mailbox does not exist or the domain has incorrect DNS, the problem is usually in the domain or hosting configuration. If everything looks correct and it only fails with one destination, it may be a policy on the receiving server.

Can I send from an external address in my form

It is not the best approach. The recommended setup is to send from a mailbox on your own domain and place the user address in Reply-To.

Does this also affect WordPress

Yes. It can appear if a contact form, store notification or other message uses a nonexistent sender or does not send through authenticated SMTP.

Conclusion

The 550 Sender verify failed error means the server cannot confirm that the sender address is valid. To fix it, review that the mailbox exists, the domain is active, the DNS and MX records are correct and the website or application is sending through authenticated SMTP.

In many cases, the issue is solved by creating the correct mailbox, adjusting the mail routing or using a valid sender in the website configuration.

If the error continues after these checks, contact miHosting support and include the full error message so they can review the domain, mail and DNS setup in more detail.