Bobcares

2 common causes for Email Error 551, and How to fix it in MailEnable, Plesk, Outlook, Thunderbird and Eudora

by | Aug 22, 2016

Email Error 551 is an SMTP error commonly seen in MailEnable servers, and is seen in two forms:

551 Sender address is not valid for your login

and

551 This mail server requires authentication before sending mail from a locally hosted domain

MailEnable is widely used in Plesk web hosting servers, and these errors are often reported to web hosting providers. As part of our Outsourced Web Hosting Support services, we use multiple strategies to resolve Error 551.

But before we get into the details, let’s see what this error means:

What is SMTP Email Error 551?

In SMTP protocol, Error 551 is shown when a sender is not found to be authorized to relay mail through the server. This is a strategy to combat spam. It can be implemented in two forms:

1. Sender or Recipient mail address not authorized

For an SMTP server to accept a mail into the queue, either the Sender’s Mail Address or the Recipient’s Mail Address should be hosted in the SMTP server.

In MailEnable servers, this is controlled by a setting called “Authenticated senders must use valid sender address“.

[ Use your time to build your business. We’ll take care of your customers. Hire Our Hosting Support Specialists at $10.94/hr. ]

2. Sender not authenticated

A mail is accepted by the server only if the sender is authenticated using a password.

In MailEnable servers, the setting “Senders from local domains must authenticate to send email” is used to enable this feature.

RELATED : How to fix email error “554 5.7.1 : Relay access denied”

How to fix Error 551 in MailEnable servers

Mail sending through SMTP authentication is a powerful way to block spammers. So, we recommend web hosting providers to keep the setting “Senders from local domains must authenticate to send email” enabled at all times.

However, the setting “Authenticated senders must use valid sender address” is seen to cause more harm than good. So, for servers in which Error 551 is common, we recommend disabling this option.

It can be done by going to SMTP Properties >> Security tab.

[ Running a hosting business doesn’t have to be hard, or costly. Get world class Hosting Support Specialists at $10.94/hour (bulk discounts available) ]

Fixing Error 551 in mail clients like Outlook, Thunderbird, Eudora, etc.

Some web hosts value the additional security of the default MailEnable settings. In those cases, we (as the web host’s support team) help web masters configure their mail clients.

Here’s how:

1. How to fix “551 Sender address is not valid for your login”

This error is returned by the mail server while sending mail, and is displayed by in email clients such as Outlook Express.

Email error 551 - Sender address is not valid for your login

Email error 551 – Sender address is not valid for your login

This error is caused by an anti-spoofing feature in MailEnable servers, which can be set by enabling “Authenticated senders must use valid sender address” in order to prevent spoofing.

The best solution is to disable this setting in MailEnable. However, if it cannot be done, mail client settings need to be reviewed. Here’s how:

Verify the login details of the email account configured in the email client and confirm that it matches the actual email account.

For instance, if your email account is bob@bobcares.com, then it should be specified in the logon information and all the e-mail address fields in Outlook.

 

Email error 551 - How to solve in Outlook Express

Verify the email account settings in Outlook

 

2. How to fix “551 This mail server requires authentication before sending mail from a locally hosted domain”

This is another error 551 that happens when you try to send email from the email client using MailEnable email server, without properly authenticating it.

The error message shown in the email client, say Outlook, would be as:

The server rejected the sender address. The server response was: 551 This mail server requires authentication before sending mail from a locally hosted domain. Please reconfigure your mail client to authenticate before sending mail.

This error 551 occurs when “SMTP authentication” is not enabled in your email client. The solution is to configure your mail client to use SMTP authentication.

In Outlook, the option ‘My server requires authentication‘ in the ‘Outgoing Server‘ section should be checked to enable authentication.

Before sending email, authenticate the account by providing the mail account username and password.

Email Error 551 - Enable SMTP authentication in email client

Enable SMTP authentication in Outlook

 

 

Email Error 551 - SMTP authentication in Thunderbird mail client

SMTP authentication in Thunderbird mail client

 

There are two other workarounds for this error in the MailEnable server, which are not commonly recommended due to security reasons:

  1. This 551 error occurs because MailEnable security feature doesn’t permit spoofing. Disabling this security feature by selecting the option: “Anyone can spoof sender addresses“, will prevent this error.
  2. Another workaround is to allow relaying for trusted IP addresses. The setting “Allow relay for privileged IP ranges” in MailEnable can be used to permit relaying for certain IP addresses and to prevent such error messages.

The 551 error message ‘This mail server requires authentication before sending mail from a locally hosted domain‘ has many variants:

  1. 551 User not local or invalid address – Relay denied.
  2. 551 Relay request denied
  3. 551 This is not a relay host
  4. 551 Authentication required for relay
  5. 551 User not local; please try <FORWARDPATH>

We’ve been able to prevent server incidents by up to 15% by using our proactive server checks (click here to see how we improve web hosting support).

Other reasons for Email Error 551

Today we’ve seen the two major 551 errors in MailEnable and the fixes for that. But there maybe cases like mailbox records missing or email client setting errors, that cause the error.

Another common error 551 is “551 Mailhost is on our global blacklist” or “551 Sender is on domain’s block list“. This happens when the recipient mail server bounces email from the sender, which is in its blacklist.

551 email errors can happen in a variety of ways. Messages such as “551 No valid recipients“, “551 not our customer“, “551 Unknown user“, “551 user does not exist“, etc. shows that the recipient email address does not exist in the mail server.

The settings to fix may vary based on the email client used. Outlook Express, Thunderbird, Eudora, Microsoft Outlook, etc. are some of the commonly used email clients by our customers.

 

STOP SPENDING TIME ON SUPPORT!

Do you spend all day answering technical support queries?

Wish you had more time to focus on your business? Let us help you.

We free up your time by taking care of your customers and servers. Our engineers monitor your servers 24/7, and support your customers over help desk, live chat and phone.

HIRE SUPPORT SPECIALISTS AT $9.99/HR

Bobcares provides Outsourced Hosting Support and Outsourced Server Management for online businesses. Our services include Hosting Support Services, server support, help desk support, live chat support and phone support.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF