Email sending limits on web hosting: why they exist and how Cloud Ninza keeps your email in the inbox (2026)

Why hosting companies limit outgoing email

Every email your website or mailbox sends leaves through a mail server with an IP address. Gmail, Outlook, Yahoo and corporate filters keep a reputation score for that address: lots of wanted mail and few complaints keep it high; spam, bounces and complaints push it down. When the score drops far enough, mail from that address goes to spam folders — or is refused outright.

On shared hosting, many customers send through the same servers. That is efficient and keeps prices low, but it means one customer's spam can damage everyone's delivery. The most common cause is not a spammer buying hosting; it is an ordinary website that gets hacked — an outdated WordPress plugin, a contact form without a CAPTCHA, a leaked mailbox password — and starts sending thousands of messages overnight.

Sending limits are the seatbelt for that situation. A normal business never notices them; a hacked site hits them within minutes and stops doing damage.

Cloud Ninza's sending limits, by plan

Each project (one hosting account) has a single allowance that covers everything it sends: website mail from WordPress or PHP mail(), contact forms, apps in Node.js, Python, Java or PHP that talk to the mail server, and every mailbox you send from in Outlook, on your phone or in webmail. It is counted per recipient — one email to five people counts as five.

• Starter: 50 per hour and 200 per day
• Growth: 100 per hour and 500 per day
• Business: 200 per hour and 1,000 per day
• Pro: 300 per hour and 2,000 per day

What those numbers mean in practice

A typical small business website sends a handful of emails an hour: order confirmations, password resets, contact-form notifications and the owner's own replies. Even a busy shop on Starter rarely comes close to the hourly figure. The daily figure is deliberately lower than 24 times the hourly one, so a steady leak — a script sending a few messages every minute — is caught as well as a sudden burst.

Because the allowance is per project rather than per mailbox, adding more mailboxes does not multiply what an account can send. That matters: if ten mailboxes each had their own large limit, one stolen password would still be enough to send a mountain of spam.

What happens when a project reaches its limit

Further emails are refused at once with a clear message — "Hourly email limit reached for this hosting account" (or the daily one) — and can be sent again as the hour or the day moves on. Nothing is charged and nothing is deleted. We email you the first time it happens on a day, so a site sending mail you did not expect is noticed quickly instead of weeks later.

When sending is paused automatically

Some patterns are almost never genuine, so the platform pauses all outgoing email from the project straight away and holds any email still waiting to leave:

• The project keeps trying to send after reaching its limit — 10 refused attempts within an hour. A person stops; a spam script keeps hammering.
• 30% or more of its email bounces, once it has sent at least 20 emails in a day. High bounce rates come from bought, scraped or very old mailing lists, which mailbox providers treat as spam.

What you see, and how sending comes back

While sending is paused, your websites and apps keep running and receiving email keeps working, so no incoming message is lost. You receive an email explaining what was detected, and the Email page in your dashboard shows a red bar with the reason. Our team then checks it with you. In most cases the fix is quick: update or remove the vulnerable plugin, add a CAPTCHA to the form, change a leaked password. Sending is then turned back on; emails that were held are delivered if they were genuine, or deleted if they were spam, so they never reach anyone's inbox.

A pause is never lifted automatically. That is deliberate: if the cause is still there, the spam would simply start again.

Read this before buying extra email

Every plan includes free business email accounts on your domain, and you can add storage or move to a bigger plan for more mailboxes. Extra storage and extra mailboxes give you more space and more addresses — they do not raise the sending limit, and every mailbox on a project shares the same allowance and the same spam protection. If you plan to send large volumes, choose a plan whose limit fits, or ask us first.

Newsletters and marketing campaigns

Hosting accounts are for transactional and personal email: order and booking confirmations, password resets, invoices, replies to customers. Bulk newsletters and marketing campaigns should go through a dedicated email marketing service that manages consent, unsubscribes and complaint handling. Sending campaigns from a hosting account is against the acceptable use policy and is exactly what the automatic checks are built to stop.

How Cloud Ninza keeps the mail servers trusted

Limits are one layer. Others work alongside them:

• Cloud Ninza's own email (invoices, sign-in codes) and customers' email leave from separate IP addresses, so customer traffic can never affect our notices to you — and the other way round.
• DKIM signing is available for every website domain, and the dashboard shows the exact SPF, DKIM and DMARC records to add.
• Bounces are tracked for every project, and heavy bouncing pauses sending before it can harm anyone else.
• Mailbox logins are always encrypted, and dashboard accounts can use two-step verification.
• Every account's sending is checked every five minutes, and our team is alerted the moment something looks wrong.

How to keep your own email trusted

Most delivery problems start on the website, not the mail server. A few habits prevent nearly all of them:

• Keep WordPress, plugins and themes up to date, and remove plugins you do not use.
• Put a CAPTCHA or honeypot on every contact, sign-up and comment form.
• Use strong, unique mailbox passwords; turn on two-step verification for your dashboard.
• Add SPF, DKIM and DMARC for your domain — the Domains and Email pages show the exact records.
• Only email people who asked to hear from you, and remove addresses that bounce.

If your website is not sending email

Check the Email page first: a red bar means sending is paused, with the reason. If there is no bar, the project may simply have reached its hourly limit — wait and try again, and look at what is sending so much. If messages are accepted but not arriving, the usual cause is missing SPF, DKIM or DMARC records, which the dashboard checks for you. Our help center guide on email sending limits has the full details, and support is available 24x7.

Key takeaways

The short version, for anyone skimming:

• Shared mail servers need limits, because one hacked site could get everyone's email blocked.
• Each Cloud Ninza project has one allowance for all its email, from 50 per hour and 200 per day on Starter.
• Over the limit, email is refused until the hour or day moves on; nothing is charged.
• Spam-like sending pauses outgoing email automatically; receiving keeps working and our team helps fix the cause.
• Extra mailboxes or storage do not raise the limit — read the rules before buying extra email.