Bobcares

“Destination smtp server rejected the sender” – Here’s how to fix it

by | Nov 20, 2018

Email errors are quite frustrating especially when you do not know why it is happening!

Though the bounce mail show some error text, that will just serve as a pointer to the possible reasons for the error.

One such error is “Destination smtp server rejected the sender” shown in email marketing programs like SendBlaster.

At Bobcares, we resolve many email related errors as part of our Outsourced Technical Support services for Web hosts.

Today, we’ll see the top reasons for this error and how we fix it.

 

What is “Destination SMTP server rejected the sender” error?

In any mail transaction, there is a sending server and a recipient. All mails do not reach the destination server. At the receiving side, there are many checks to prevent fraud mails. When this receiving server has a doubt on the authenticity of the mail sender, it reject mails from such servers.

And a bounce message in such cases will look like :

Your Incoming messages could not be delivered to your email ([my email]) because the Destination SMTP server rejected the sender.

 

Causes and Fixes for “Destination SMTP server rejected the sender” error

There can be many reasons for this error. We will have a close look at them.

 

1. SMTP settings

The “sender rejected error” mainly happens when the outgoing mail server (SMTP) settings are setup wrongly in the mail clients like Outlook, Windows Mail etc.

Typically, email users set the email port wrongly.

Solution

So, when user’s report this error, our Support Engineers ensure the correct mail server settings first. This include:

  1. Correct mail server name
  2. Email port – 465 or 587
  3. Authentication type
  4. Correct email address and password

We have also seen this error in Gmail. This happens when people use an account where google-apps is not configured.

Bulk mail sending programs like SendBlaster allows direct mail sending or mails via an SMTP server.  Certain e-mail domains, for instance, hotmail don’t allow direct sends. Then the message gets rejected if it originates from a desktop system as opposed to a public SMTP server. So to fix, we configure SMTP server details to send mails successfully.

 

2. Poor IP reputation

Another reason for email failure is bad reputation of the IP from which mail originates. The reputation of the IP can go bad when there are multiple spamming instances from an IP. Eventually, the IP is blacklisted at Spam monitoring tools like SORBS, DNSBL etc.

Solution

Here, to solve the problem and send mail, we need to ensure that the mail originating IP is clean. If at all it is blacklisted, we take corrective actions on the server and request a delist. Usually de-listing happens in a few days time.

 

3. Bad DNS

Similarly, mail block can occur due to the issues in the dns records of the domain. These DNS records helps destination server to cross-check that the sender is a genuine one.

To defend spam, mail servers typically checks the following values as part of dns check. The main records are:

1. SPF record

This record tells which all IP addresses can send mails on behalf of the domain. Often, when there is a change in mail server IP, the SPF record do not contain all the IP addresses from which mail originates. As a result, it may result in the error “Destination smtp server rejected the sender”.

2. DomainKeys Identified Mail (DKIM)

DKIM is a method to prevent email spoofing. It helps to associate a domain name with an email message by affixing a digital signature to it.  As a result, the mail server can confirm whether mail originates from the valid domain itself.

3. Reverse dns

Reverse DNS is the name that matches to IP address of the server. For mails to work, the forward and reverse dns should match. That is, if a server xyz.mailserver.com points to the IP address 192.168.x.34, the reverse dns of IP should be xyz.mailserver.com

Solution

When an error pops up, our Support Engineers verify the SPF, DKIM records of the domain. When there is a mismatch, we correct it by making enough changes in the dns records.

 

Conclusion

The error “Destination SMTP server rejected the sender” can happen mainly due to reasons such as bad mail client settings, wrong dns settings of the domain etc. Today, we have seen the top 3 reasons for the error and how our Support Engineers fix them.

PREVENT YOUR SERVER FROM CRASHING!

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

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

4 Comments

  1. Ali ANik

    How i fix destination smtp server rejected the sender problem on SendBlaster.

    Reply
    • Sijin George

      Hello Ali,
      It should be something with the sender email or incompatible SendBlaster settings. Both need detailed checking. We’ll be happy to talk to you on chat (click on the icon at right-bottom).

      Reply
  2. Abel Glomo

    please How i fix destination smtp server rejected the sender problem on SendBlaster.

    Reply
    • Maheen Aboobakkar

      Hello Abel,

      Because you are using SendBlaster as a mail client, you must configure your SMTP settings in order to send emails correctly:

      Sendblaster > Send button > Send Settings > Fill out the form details > Connection test.

      SMTP server: your SMTP server’s name.

      Authentication required: flag it if you want to send authenticated emails. Read our general article about how to configure an SMTP server to know more.

      Username: your email address.

      Password: your password. If you’re using turboSMTP, it’s the one that has been given to you after the subscription.

      Port: the default port for SMTP is 25, but you can choose among different ones depending on your connection.

      We’ll be happy to talk to you on chat (click on the icon at right-bottom).

      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