Skip to content

Email Greylisting: What It Is and How It Affects Sending

What email greylisting is, why it delays cold email, and how it affects email verification results.

Nov 14, 2026 4 min read 948 words
Email Greylisting: What It Is and How It Affects Sending

Email greylisting is a spam filter trick that temporarily refuses mail from a sender the server does not know yet. A real mail server tries again later and gets through. Many spam tools do not. For anyone who sends cold email or verifies lists, email greylisting explains why a message arrives late and why a verification result can come back as "unknown".

Email greylisting explained cover
Email greylisting explained cover

What is email greylisting?#

With email greylisting, a receiving server answers the first delivery attempt from an unfamiliar sender with a temporary error. It does not say "never". It says "try again later". A legitimate mail server keeps the message in its queue and retries. Many bulk spam senders do not retry, so the spam never lands.

The receiving server often remembers a combination of the sending server's address, the sender and the recipient. The first time it sees a new combination, it defers. On a later attempt, it accepts.

How does it work, step by step?#

  1. Your server connects and tries to deliver a message.
  2. The receiver does not know the combination yet. It replies with a temporary failure, a 4xx code in SMTP.
  3. Your server holds the message and schedules a retry. RFC 5321 describes retry behaviour for temporary failures in its section on sending strategy.
  4. The retry arrives after the receiver's wait time.
  5. The receiver accepts the message and often remembers the sender for future mail.

For you, the effect is a delay. It can last minutes or longer, depending on the receiver's setting and your server's retry schedule.

Why does email greylisting matter for cold email?#

Three things change when you send to a domain that greylists:

  • Delays. A first email to a new contact may arrive late. Do not judge a campaign on the first hour.
  • Retries from tools. Cloud email services retry for you. A cheap or poorly built sender may give up after a single attempt, and the message is lost.
  • Fresh sending IPs. A new IP or domain is unknown to every receiver, so the first messages to a greylisting domain are more likely to be deferred.

None of this is a spam verdict. Greylisting says "not yet known", not "bad".

Email greylisting and email verification#

Verification tools talk to the mail server before you send. If the server answers with a temporary error because of greylisting, the tool cannot confirm the mailbox. The result is often "unknown" or a flag that marks the address as greylisted.

Tomba's verifier outputs include a greylisted flag among its flags, next to accept_all, block, disposable, webmail and gibberish. The status field uses valid, accept_all, invalid, unknown or disposable. You can check any address with the Tomba Email Verifier.

What to do with an "unknown" result from a greylisting domain:

  1. Verify again later. A second attempt may succeed once the server has seen the sender.
  2. Check the other signals in the result, such as the score and the sources.
  3. Send a small test batch and watch for bounces before you send the full list.

For more on how catch-all domains compare, see the catch-all verifier.

How do you know a message was greylisted?#

Look at your sending logs or the bounce notice:

  • A 4xx reply means a temporary failure. Your server will retry.
  • A 5xx reply is a permanent failure. It will not retry. That is a bounce.
  • A message in your outbox with "deferred" status is waiting for a retry.

Your email service's activity log usually shows deferred messages with the reply text from the receiver. Words like "try again later", "greylisted" or "temporarily deferred" point to greylisting.

Best practices when you send to greylisting domains#

  • Use a sender that retries. Reputable email platforms and servers do. Check yours.
  • Warm up new domains and IPs. Send small volumes at first and grow slowly. See the email warmup calculator.
  • Keep sending patterns steady. Sudden jumps look suspicious.
  • Clean your list. Verify addresses so bad ones do not mix with deferred ones. Real bounces are easier to spot on a clean list.
  • Be patient. Wait before you declare a message lost. Give it a day if the log shows deferral.

Should you use greylisting on your own server?#

If you run your own mail server, greylisting can cut spam with little effort. The cost is delayed mail from new senders, which can annoy users waiting for a sign-up link or a receipt. Some teams exempt known senders or only apply it to suspicious traffic. Test it on a small group before you roll it out.

A quick example#

Imagine you email a new contact at a company that uses email greylisting. Your first attempt gets a temporary reply, so your platform marks the message deferred. Twenty minutes later it retries and the message is accepted. The contact sees it with a short delay and never knows anything happened.

Frequently asked questions#

Does email greylisting mean my email is spam?#

No. It means the receiver does not know the sender yet. A retry usually succeeds.

How long does a greylisting delay last?#

It depends on the receiver's settings and your server's retry schedule. Treat it as minutes to hours, not days, and check your logs.

Why does a verifier return "unknown"?#

Sometimes the server answered with a temporary error, so the mailbox could not be confirmed. Try again later.

Can I bypass greylisting?#

You do not need to. Send from a server that retries, and keep your sending steady.

Verify before you send#

Check your list with the Tomba Email Verifier so the emails you send are ones you have reason to trust.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?