OrbiSearch
← Back to blog

Greylisted Emails: Single Verification Now Resolves Them

Until today, a single verification that hit a greylisting mail server came back as Unknown, because the server deferred the check instead of answering it. Now you can get the real answer. Add retry_greylisted=true to a /v1/verify request and we wait, retry once and return Safe, Invalid or Risky.

It's live now for every API account, off by default, at no extra cost.

What is greylisting?

Greylisting is an anti-spam technique. When a mail server sees a sender it doesn't recognise, it temporarily refuses the first attempt and only accepts a retry that arrives a little later, usually after about a minute. Real mail servers retry automatically, while most spam tools don't bother.

Greylisting is most common on companies protected by Mimecast, but other mail servers use it too.

Why do greylisted emails come back as unknown?

To verify an email address, we ask the recipient's mail server whether it would accept mail for it. A greylisting server doesn't answer that question on the first attempt. It just says "try again later". Without a retry there is no answer to report, so until now a single verification that hit greylisting came back as Unknown with the reason greylisted.

That is common. On a typical day about 1 in 7 single verifications we run comes back greylisted, and for companies protected by Mimecast it's more than half of all checks.

How bulk verification handles greylisting

Bulk verification has always handled this. When a bulk job hits a greylisting server, we retry it for you in the background and return the real result. You rarely see "greylisted" in a finished bulk job.

How to resolve greylisted emails with the single verification API

Add retry_greylisted=true to your request:

curl --request GET \
  --url "https://api.orbisearch.com/v1/[email protected]&retry_greylisted=true" \
  --header "X-API-Key: YOUR_API_KEY"

When the mail server defers, we wait about a minute, retry once within the same request, and return the real answer: Safe, Invalid or Risky.

In our tests every retried Mimecast check answered, and more than 8 in 10 came back Safe or Invalid. If you've seen "greylisted" in your results, those are the emails this now answers.

What to know before you turn it on

  • It's off by default. Your existing integration works exactly as before until you add the parameter.
  • Only greylisted checks wait. They take about 60 to 75 seconds in total. Everything else returns as fast as it does today.
  • timeout still caps the whole request. Set it to at least 80 seconds (the default of 97 works). A lower value returns a 422 explaining why.
  • Your HTTP client has to wait too. Many HTTP clients and no-code tools give up after 30 or 60 seconds, so raise their timeout to match.
  • Same price. 0.2 credits per verification, with or without a retry.

The full details are in the single verification guide.

Frequently asked questions

What does "greylisted" mean in an email verification result?

It means the recipient's mail server deferred the check and asked the sender to try again later, so the check ended before the server said whether the address exists. It doesn't mean the address is bad.

Is a greylisted email valid?

Not necessarily. Greylisting tells you nothing about the mailbox itself, only that the server wanted a retry. With retry_greylisted=true, OrbiSearch makes that retry and tells you whether the address is safe, invalid or risky.

Does Mimecast use greylisting?

Yes. Mimecast is the most common source of greylisting we see. For companies protected by Mimecast, more than half of single verifications are greylisted on the first attempt.

What happens if the server still defers after the retry?

The result is Unknown with the greylisted reason, the same as without the parameter. The same applies if not enough of your timeout is left for the retry.

Should I use bulk or single verification for greylisted emails?

If you're checking more than one address, use bulk verification. It retries greylisted servers in the background for longer and doesn't hold a request open. Use retry_greylisted=true when you need one address answered in real time, for example in Clay or a signup form.

If you have questions or see a result that looks off, get in touch and we'll look into it.