Bobcares

How to fix ‘550 5.1.1 : Recipient address rejected’ error in Exchange and Postfix servers

by | Sep 22, 2016

In our role as Website Support specialists for web hosting companies, we’ve seen internet users sending emails to certain recipients encountering the error:

550 5.1.1 <user@domain.com>: Recipient address rejected

This error is associated with recipients whose emails are hosted in Exchange and Postfix servers. Today we’ll discuss the reasons for ‘550 5.1.1’ error and how to fix it.

See how we can support your websites!

How to fix error ‘550 5.1.1 : Recipient address rejected’

This 550 error can happen due to two main reasons:

1. Issues related to the recipient server

The common issues that can happen with the recipient end are:

a. Recipient address wrongly specified in the email

Many often, the error is caused by a very simple reason – incorrect email address given in the email. Sometimes a typo in the address can often lead to emails bouncing.

If the email is addressed to a non-existing account or account that is no longer in use in the recipient server, the recipient server would be unable to find the email account.

In such cases, the email would fail to deliver to the recipient and would be bounced to the sender, with the error ‘550 5.1.1 : Recipient address rejected’.

Solution:

Double-check the email address you’ve given in the email for spelling errors and confirm its a valid email account.

Also check that the domain is resolving to the correct server from your end and the routing is fine, using ‘dig’ and ‘trace route’ tools.

b. MX record for the recipient domain resolving to the wrong server

If the MX record for the recipient domain is resolving wrongly to some other remote server, then the email will not be routed to the correct mail server.

As a result, the mail server that received the mail will not be able to track the email account in it and hence mail delivery will fail. To confirm the MX records for a domain, use the command:

dig domain.com MX

DNS issues can also happen due to wrongly set DNS records such as wild card entries for the domain or priority for MX records set wrongly.

Solution:

If any issues noted in the MX records for the recipient domain, contact the support for the server and get it sorted out. If the recipient server is yours, edit the DNS records and fix the issues.

In addition to the MX records, email routing within the server should also be checked. Verify that the emails are routed to the correct server and not any remote servers.

[ A single misconfiguration may break your site! Click here for a customized and error-free website to help you boost your business. ]

c. Configuration settings in recipient mail server

Many recipient servers implement custom security settings in the mail server to avoid unwanted mails from abusing the server. Spam filters are major tools that block emails.

These security rules are implemented in the form of server-wide firewalls or domain-specific filters. A wrongly set email forwarder can also lead to incorrect email routing.

Certain ‘Message Delivery Restrictions’ for the recipient email account that may be blocking specific senders, can also end up giving error ‘550 5.1.1 : Recipient address rejected’.

Solution:

To verify that the recipient server firewalls are not blocking your server, do:

telnet domain.com 25

If connectivity issues or email filters are blocking your emails, get the recipient domain filters and blacklists verified to rule out such blocks.

2. Issues with sender server

The 550 5.1.1 error can be caused due to issues at sender server too:

a. Sender is suspected for spamming

Many mail servers such as Postfix and Exchange have features to reject non-verifiable senders. Verifying senders can include checking SPF records to RDNS.

If the sender domain is in blacklist such as Spamhaus, the recipient mail server may reject mails from the server.

Solution:

Verify that SPF records exist for the sender domain and RDNS is configured correctly. The command to verify RDNS is:

host IP address

Confirm that your server is not listed in any blacklists. If blacklisted, audit the server for any spamming scripts and secure the server against spammers.

[ Worried about your broken website? Get our server specialists’ assistance to fix your site from all errors. ]

b. Sender email account hijacked

If there are numerous bounce messages noted in the mail logs, it can denote that someone is using the sender email account for spamming.

Even certain spamming scripts can send mass mails to different non-existing accounts, causing the logs to be filled with ‘550 5.1.1’ bounce errors.

Solution:

Examine the email logs and confirm if any spamming is happening in the server.

Lock the suspicious email account without delay and change the password to a strong one. Audit the server for malicious scripts and implement strict password policy.

[ Are your websites helping you get business? Our website support team gives you custom website solutions and fix all errors in your website in no time. ]

c. Configuration issues in sender server

In rare cases, it has been noted that the recipient domain is configured as a local domain in the sender server. In such cases, domain would resolve incorrectly and email error happens.

Certain mail servers have outbound mail filtering configured in them, which can block the emails going out from it, and leading to email rejection messages.

Solution:

Check email routing within the sender server by sending test mails and checking the logs for messages. Also verify that the outbound filter rules are not blocking the mails.

In short..

Today we discussed the various reasons for ‘550 5.5.1 : Recipient address rejected’ error and how to fix those.

Though this error is common in Exchange and Postfix, users who send to these servers may see the error, even if they are in other mail servers.

Since senders use email clients such as Outlook or Thunderbird to send mails, they will see the message in their email clients.

The other variant for the error ‘550 5.5.1 : Recipient address rejected’ are:

550 5.1.1 : The email account that you tried to reach does not exist
550 5.1.1 : User unknown
550 5.1.1 : Recipient address rejected: User unknown in virtual alias table
550 5.1.1 <user@domain.com>: Recipient address rejected: User unknown in relay recipient table

Checking the email logs, configuring email clients and mail servers correctly, securing the servers against spamming and spoofing, etc. are crucial in email error debugging.

If you’d like to know how to secure your mail server and prevent email bounce errors, we’d be happy to talk to you.

 

 

Is your website stable and unique for your business?

Don't let a poor website design or site errors affect your business. We're here to help you.

CLICK HERE TO GET AN ERROR-FREE SITE

var google_conversion_label = "Blp0CLCojHIQ0aD71QM";

4 Comments

  1. james

    for me was a mail server issue where my mail server would not receive mail. i was accepting mail from james@xyz.com, then wanted to add james@abc.com.

    step 1
    create virtual domain table using postmap
    step 2
    add virtual domain entry in main.cf
    step 3
    create virtual table using postmap (“man 5 virtual”)
    step 4
    add virtual entry in main.cf

    step 3 file format (“man 5 virtual”)
    /etc/postfix/virtual:
    virtual-alias.domain anything (right-hand side does not matter)
    postmaster@virtual-alias.domain postmaster
    user1@virtual-alias.domain address1
    user2@virtual-alias.domain address2, address3

    line 1 (virtual-alias.domain anything) is ABSOLUTELY required.
    james@abc.com james #this name maps to james@xyz.com
    james@123.com james #etc etc etc..

    then use postmap to hash it and do postfix reload.

    step 4 file entries
    in main.cf:
    virtual_alias_maps = hash:/etc/postfix/virtual
    virtual_alias_domains = hash:/etc/postfix/virtual_domains

    Reply
  2. Susan E. Greene

    I don’t see my problem among these:
    :Server error: 550 5.1.1 relaying not allowed.

    As far as I know, my sister is not forwarding emails and I’m not at my Army site when I send a test msg. This started recently and a scan did not correct

    Reply
    • Just a friend

      A scan will not correct because it’s not related. Has nothing to do with your problem.

      Reply
  3. pastebin

    Thanks for information… ☺

    Reply

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