Email refused: account reached its limit of emails per hour
Every hosting account may send a limited number of emails per hour. The limit stops a hacked website from sending thousands of spam messages and getting the server's address blocklisted for everyone. Mail from websites and scripts over the limit is not lost: it waits on the server and goes out later. A mail app gets an error instead and can send again later.
Symptoms
- A mail app shows, or a bounce contains:
451 4.7.1 This account reached its limit of 500 emails per hour. Try again later. - Mail from your website or newsletter arrives late, in batches.
- You and the administrator got an email that the account reached its hourly limit.
Causes
- A newsletter or bulk mailing sent from a mailbox, a website plugin or a script.
- A hacked website or a stolen mailbox password is sending spam.
- A form or cron job sends a mail per visitor or per minute without you noticing.
What counts: each recipient of every message from the account — from mailboxes, websites (PHP mail()), scripts, cron jobs and mailing lists alike. A message to 50 recipients counts 50.
Fix
See how much your account sent
Open Email Accounts (section Email). The top of the page shows how many emails the account sent in the last hour and the limit. Delivery reports (direction Outgoing) shows each message.
1. Bulk mailings
- Spread a mailing over several hours, or send it through a newsletter service.
- For mailing lists of your own, ask your host for a package with a higher Emails per hour.
2. Hacked website or mailbox
If you did not send that mail:
- In Delivery reports, look at the From addresses and recipients of the outgoing mail.
- Change the password of the mailbox that sent it (Password next to the mailbox).
- Open Security (section Advanced) and click Scan my website; update WordPress, plugins and themes (WordPress page → Update everything).
- Contact your host through Support.
3. Forms and scripts
Find the form or cron job that sends too often (the From and To addresses and the times in Delivery reports usually point to it), and add a captcha or lower its frequency.
For administrators
- The server default is set in Mail Queue & Spam (section Email) → Sending limits → Default emails per hour, per account (default
500,0= no limit). - A package can set its own Emails per hour (0 = server default).
- Sending limits shows each account's sending in the Last hour, Accounts that reached their limit and Messages held back.
Still not working?
If mail is still refused long after an hour, contact your host: they can see whether the account's mail is being held or rejected for another reason.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Cannot send email: SMTP authentication failed
Your mail app or website cannot send: "SMTP authentication failed", refused or timed out. Check the username, ports 465/587, bans and the error.
- Emails you send go to spam (Gmail, Outlook)
Your mail lands in spam or is rejected as unauthenticated. Set up SPF, DKIM and DMARC from the Email deliverability table and check the usual causes.
- Outgoing email stuck in the queue (port 25 blocked)
Mail to Gmail, Outlook and others stays "deferred" with connection timed out. Check if your server provider blocks outgoing port 25 and get it opened.