25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

Need help?

Our experts have had an average response time of 11.43 minutes in March 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

How to fix “550-previous (cached) callout verification failure” email error

by | Oct 12, 2018

Spammers have made life difficult for us all.

These days even legitimate mails get snagged in the vast array of anti-spam defenses deployed by companies.

One such commonly misclassified anti-spam bounce is:

user2@recipient.com
SMTP error from remote mail server after RCPT TO::
host mx.sender.com [x.x.x.x]: 550-Verification failed for 
550-Previous (cached) callout verification failure
550 Sender verify failed

Here at Bobcares, we resolve such errors as part of our Outsourced Tech Support services for web hosting providers. Today we’ll cover what we’ve seen as the cause of this issue, and how we fix them.

 

What is the error “550-Previous (cached) callout verification failure”?

Spammers often use fake email addresses set as their “FROM” address.

That is why you get spam from prince@nigeria.com.

So, some mail servers test the validity of a “FROM” email ID before the mail is accepted. This anti-spam check is called Sender Verification Callout.

When this verification fails, the mail is rejected with the error: 550-Verification failed.

Server administration panels like cPanel & WHM provides this feature.

550-previous (cached) callout verification failure

 

How cached results block legitimate mail users

We’ve seen cases where improperly setup mail accounts, or those with permission errors often fail the Sender Verify Callout test.

A reset of the mail accounts usually fixes this error.

However, they would still receive the “550-Verification failed” error when sending to some servers.

That is caused due to Verify Callout results caching by those servers. Mail servers cache these results to improve mail delivery speed.

The error shown in such cases is: 550-previous (cached) callout verification failure

 

How to fix the verification failed error

As part of our technical support service for web hosts, we see support requests that say:

“My colleague is unable to mail me. My server keeps rejecting the mail with “550-previous (cached) callout verification failure”. They had a mail issue which they fixed, but they’re still unable to contact me.”

It is caused by the Sender Verification Results being cached.

To fix this, we use two ways:

 

1. Clear the sender verification cache

The verification results are stored in a file called /var/spool/exim/db/callout. We delete this file so that the address is verified afresh.

 

2. Disable Sender Verification Callout

If we see from the mail logs that this anti-spam check is causing more trouble than help, we disable it.

 

Conclusion

“550-Previous (cached) callout verification failure” error is caused when the mail server caches the results of old “Sender Verify Callout” anti-spam checks. Today we’ve seen two ways to fix this error.

 

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";

0 Comments

Submit a Comment

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

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

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

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