SMTP Error 450: Mailbox Unavailable - Busy or Temporarily Blocked
SMTP Error 450 means “Mailbox Unavailable - Busy or Temporarily Blocked.” The recipient mailbox is temporarily unavailable. This soft bounce can be caused by greylisting, temporary mailbox locks, server-side processing, or anti-spam measures that require senders to retry.
Jun 10 09:14:52 mx postfix/smtpd[20413]: NOQUEUE: reject: RCPT from mail.example.net[203.0.113.10]: 450 4.2.0 <rcpt@example.com>: Recipient address rejected: Greylisted, please try again in 300 seconds; from=<sender@example.net> proto=ESMTP
What does 450 mean?
SMTP code 450 indicates the requested mailbox is temporarily unavailable. Unlike the permanent 550 error, a 450 means the delivery might succeed if retried later. This code is commonly used by greylisting systems, which deliberately reject first-time sender/recipient pairs to filter out spam bots that typically do not retry.
Many anti-spam systems use 450 as a deliberate filtering mechanism. Postfix greylisting, for example, returns 450 on the first delivery attempt and accepts the email on the second attempt (usually 5-15 minutes later). If you are seeing 450 bounces consistently, ensure your MTA is configured to retry. Single occurrences of 450 are completely normal and expected.
How 450 plays out
450 replyWhere 450 sits: soft vs hard bounce
| Soft bounce (4xx) | Hard bounce (5xx) | |
|---|---|---|
| Nature | Temporary | Permanent |
| SMTP class | 4xx | 5xx |
| What to do | Let it retry | Suppress the address |
| Recoverable? | Often | No |
| 450 is | ✓ this code |
Common causes of 450
- Greylisting - server deliberately rejects first delivery attempt
- Mailbox temporarily locked for maintenance or migration
- Anti-spam system requesting retry to verify legitimate sender
- Server-side processing delay (virus scanning, content filtering)
- Rate limiting applied to the specific recipient or domain
How to fix 450
- Ensure your MTA has proper retry logic (most handle this automatically)
- Wait 5-15 minutes for greylisting, then retry
- If persistent across many recipients at the same domain, check your sender reputation
- Verify your sending IP is not blacklisted using a Blacklist Checker