# Error: 447 Message or recipient limit reached

Source: https://catalystgroup.gg/docs/email-delivery/error-447-message-limit/
Updated: 2026-10-19 · By Duane Garner

The mail server has temporarily stopped accepting mail from you because you passed its message or recipient limit. Slow down and retry later.

> **Shown by SMTP-based sending (Other SMTP, Zoho Mail, the backup SMTP transport):** The test result or the error log shows a reply starting with `447`, saying a message or recipient limit was reached.

 

This article is for site owners sending through an SMTP server who get a 447 reply.

 

## What this error means

 

Code 447 is not one of the core SMTP reply codes, but some mail servers and hosting providers use it to say you have sent too many messages, or to too many recipients, within their time window. The leading 4 means the refusal is temporary. Once the window passes, the server accepts mail again.

 

This is the server's own throttle. It is separate from any plan quota at a mail service, though the effect is similar.

 

## Common causes

 
- A burst of mail, such as a plugin notifying all members or customers at once.
- Messages addressed to many people at a time, including long CC or BCC lists.
- A shared hosting mail server with low hourly limits per account.
- A form abused by bots that sends many notifications quickly.
- A plugin stuck in a loop, sending the same message repeatedly.

 

## How to fix

 
1. Find what used the limit
  Open **CRM-NG SMTP → Settings → Email Log** and look at recent volume, subjects and recipients. Stop any loop or abused form first.
2. Ask about the limit
  Ask your mail provider or host what the hourly and daily message and recipient limits are for your account.
3. Set rate limiting below it
  Go to **CRM-NG SMTP → Settings → Misc** and set **Email Rate Limiting** under the provider's numbers. Extra emails are queued and sent when allowed, instead of failing.
4. Send fewer recipients per email
  Keep each message to a handful of recipients. Send separate messages rather than one message with a long BCC list.
5. Retry later
  After the window has passed, go to **CRM-NG SMTP → Tools → Email Test**, fill in **Send To** and press **Send Email**.

 

## Verify it worked

 

The test page shows "Test email sent successfully! Check your inbox to confirm delivery." With rate limiting in place, the Email Log shows queued mail going out over time without new 447 failures.

 

## Notes

 
- If your normal traffic is higher than the server allows, the fix is a mail service built for that volume, used through an API mailer.
- Messages refused with 447 are not retried by CRM-NG SMTP. If bodies are stored in the Email Log, open a failed entry and use **Resend email**.

 

## Related

 
- [Other SMTP mailer guide](https://catalystgroup.gg/docs/email-delivery/mailer-other-smtp/)
- [Zoho Mail mailer guide](https://catalystgroup.gg/docs/email-delivery/mailer-zoho/)
- [Misc settings](https://catalystgroup.gg/docs/email-delivery/misc-settings/)
- [Error: Email sending limit reached](https://catalystgroup.gg/docs/email-delivery/error-email-sending-limit/)
- [Error: 452 4.5.3 Domain policy size per transaction exceeded](https://catalystgroup.gg/docs/email-delivery/error-452-size-per-transaction-exceeded/)
- [Troubleshooting email delivery](https://catalystgroup.gg/docs/email-delivery/troubleshooting/)