Map Extract

451 4.7.1 Greylisted, try again after some time means the receiving server has not seen your combination of sending IP, envelope sender and recipient before, so it refuses the first attempt on purpose. A correctly configured sender retries a few minutes later from the same server with the same envelope, and the message goes through. You do not need to change the message or contact anyone. You need a sending setup that retries, and retries consistently.

Greylisting is one of the transient codes in our SMTP error codes guide for cold email. It is common at Zoho Mail, hosting companies' mail servers and security gateways such as Mimecast.

What the receiving server records

RFC 6647, which describes greylisting, recommends that receivers "implement greylisting based on a tuple consisting of (IP address, RFC5321.MailFrom, and the first RFC5321.RcptTo)". In plain terms the receiver keeps a small table:

FieldFictional example
Connecting IP203.0.113.17
Envelope sender (MAIL FROM)[email protected]
First recipient (RCPT TO)[email protected]
First seen09:02:11
StatusWaiting

The first time it sees this combination it answers with a 4xx code and notes the time. When the same combination returns after the minimum delay, it accepts the message and usually stops greylisting that combination, or that IP, for a while. RFC 6647 suggests remembered entries should last "at least one week" without traffic before being deleted.

The theory is that spam software often fires once and never retries, while real mail servers follow RFC 5321 and queue the message. RFC 6647 also says plainly that clients "need to be equipped to retry in order to be considered fully capable".

The reply codes vary. RFC 6647 recommends 421 or 450; in practice you will also see 451:

451 4.7.1 Greylisted, try again after some time
450 4.2.0 <[email protected]>: Recipient address rejected: Greylisted, see http://postgrey.example/
451 Internal resources are temporarily unavailable.

The third line is Mimecast's wording, which Mimecast says usually means greylisting or a poor IP reputation.

Typical retry windows

SourceWhat it says
RFC 6647Default acceptance window "SHOULD be from one minute to 24 hours" after the first attempt; a retry outside the window is treated as a new message
RFC 6647 exampleA minimum age "such as 30 minutes since the initial connection attempt"
MimecastSending server should retry after one minute to 12 hours
RFC 5321General retry interval "SHOULD be at least 30 minutes"; give-up time at least four to five days

So a sender that retries after 5 to 30 minutes, then at growing intervals, will get through almost every greylisting server on the second or third attempt. A sender that retries after 10 seconds may hit the minimum delay and be greylisted again; RFC 6647 also warns that aggressive retry schedules can trigger separate rate limits.

Why shared IP pools look like new senders

The most common reason a message is greylisted "forever" is that each retry arrives as a stranger.

  • Rotating outbound IPs. Large providers send from pools. If attempt one leaves from 203.0.113.17 and attempt two from 203.0.113.42, the tuple is new and the clock restarts. RFC 6647 describes exactly this: "a site with multiple outbound MTAs sharing one queue" may be greylisted again when a retry leaves from a different IP.
  • Changing envelope sender. Some tools put a unique bounce address in MAIL FROM for each attempt (for bounce tracking). RFC 6647 warns that a client that changes MAIL FROM between retries "may never get delivered".
  • Switching routes. If your sending software fails over to a different SMTP account or server after a deferral, the retry comes from a different IP and sender.
  • Multiple receiving servers. RFC 6647 notes that if a domain's inbound servers do not share a greylisting database, a retry landing on the second server is refused again. That is the receiver's problem, but it explains occasional double delays.

Large, reputable providers are often exempted by receivers (RFC 6647 says known senders "SHOULD be allowed to bypass the filter"). Small and new senders are not, which is why cold senders on their own domains meet greylisting more often.

Greylisting or rate limiting?

They look similar in logs, and the fixes are opposite: greylisting wants you to retry, rate limiting wants you to stop.

SignalGreylistingRate limiting or reputation deferral
Typical text"Greylisted", "try again after some time", a link to a greylisting policy"rate limited", "unusual rate", "low reputation", "too many", "temporarily deferred"
Who sees itFirst message to a new recipient or domainMany recipients at one provider at once
What a correct retry doesGets through, usually first timeFails again until volume drops
Volume dependent?NoYes
ExamplesZoho 451 4.7.1 Greylisted, Postgrey 450 4.2.0 ... GreylistedGmail 421 4.7.28, Yahoo 421 4.7.0 [TSS04], Outlook.com 421 RP-001
Your actionLet the queue retry from the same serverPause that provider and reduce volume

Yahoo's guidance groups 421 and 451 together as temporary errors that should be retried later, and adds that persistent deferrals deserve a look at its sender requirements. If a "temporary" error survives several correct retries over a few hours, it is not greylisting. See 421 4.7.0 try again later for the rate-limit cases, including Yahoo's TSS04 deferrals.

Checklist for sender retry settings

Whatever sends your mail, check:

  • 4xx replies are queued, not bounced. A tool that records a 451 as a failure and moves on loses the message.
  • First retry after 5 to 30 minutes, then at growing intervals. Not seconds, not a fixed hour.
  • Retries leave from the same server or IP. If you use a pool, check whether the provider keeps a message on the same IP.
  • The envelope sender stays identical across attempts.
  • Failover to another route is not used for greylisting replies, or you accept the extra delay it causes.
  • A sensible give-up time. A day is enough for a cold message; general mail servers use four to five days.
  • Expired messages are recorded as expired, not as invalid addresses, so you do not suppress real people.
  • You can see the queue, so you know which messages are waiting and why.

If you send through a mailbox provider's SMTP (Microsoft 365, Google Workspace, Zoho), their servers handle the queue and retries after they accept your message; greylisting by the recipient only delays delivery. The checklist matters most when you run your own mail server or a tool that talks directly to recipients' servers.

How Map Extract helps

Map Extract's bulk email sender submits messages to your own SMTP accounts, such as a Microsoft 365, Google Workspace or hosting mailbox. Once your provider has accepted a message, your provider's servers deal with any greylisting at the recipient, so the delay happens there, not in Map Extract.

What Map Extract adds around that:

  • Accepted is a separate state. The outbox distinguishes queued, accepted and uncertain items, and a sent status means your mail server accepted the message, not that it has been delivered past a recipient's greylisting.
  • Uncertain sends are not repeated. If a submission fails ambiguously after the message data, the item is marked Uncertain and not resent automatically.
  • Failover is between your own routes. If several eligible SMTP routes are configured, a failed submission can move to another one; that changes the sending server, so do not rely on it for greylisting, which wants the same server.
  • Steady pacing. Caps, minimum delays and an optional warm-up ramp mean fewer first-contact messages hit the same recipient domain at once.

Map Extract's documentation does not describe a configurable retry schedule for 4xx replies, and it does not run its own mail server. If greylisting delays are causing problems, look at your SMTP provider's queue first.

Key takeaways

  • Greylisting refuses the first attempt from an unfamiliar IP, sender and recipient combination.
  • A correct retry from the same server with the same envelope sender gets through, usually within minutes.
  • Rotating IPs, changing MAIL FROM and failing over to another route make every retry look new.
  • Greylisting wants a retry; rate limiting wants you to slow down. Read the text to tell them apart.
  • Never record a greylisted or expired message as an invalid address.

Frequently asked questions

What does 451 4.7.1 Greylisted, try again after some time mean?

The receiving server does not recognise your combination of sending IP, envelope sender and recipient, so it temporarily refuses the first attempt. A legitimate mail server queues the message and retries; once the retry arrives after the minimum delay, the receiver accepts it and usually remembers you. Nothing is wrong with your message or address. You only need a sender that retries properly.

How long does greylisting delay an email?

Usually minutes. RFC 6647 recommends that receivers accept a retry arriving from one minute to 24 hours after the first attempt, and Mimecast says senders should retry between one minute and 12 hours. Most real-world delays are under half an hour, depending on how quickly your server retries. Repeated delays every time point to a retry problem on the sending side.

Why does my email keep getting greylisted?

Usually because the retry does not look like the same message. If retries leave from a different IP in a pool, or the envelope sender changes between attempts, the receiver sees a new combination and greylists again. Some sending tools also never retry at all. Check that retries use the same server and the same MAIL FROM address.

Is greylisting the same as being rate limited?

No. Greylisting refuses the first attempt from an unfamiliar sender and accepts a correct retry, whatever your volume. Rate limiting refuses mail because you are sending too much, or too much unwanted mail, and retries keep failing until you slow down. Greylisting text says greylisted or similar; rate limit text mentions rate, volume, reputation or unusual traffic.

Sources

  1. RFC 6647: Email Greylisting: An Applicability Statement for SMTP
  2. RFC 5321: Simple Mail Transfer Protocol
  3. Mimecast: Rejected and deferred message codes
  4. Yahoo Sender Hub: SMTP error codes

Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top