Email sending limits

The hourly outbound limits for each WebGee plan, what counts towards them, and why marketing email must go through a separate service.

Outbound mail is limited per domain per hour. Applies to all shared, reseller and Workspace plans.

All outbound mail is relayed through a dedicated service included with every account, so delivery does not depend on the reputation of your server's own IP address — see Outbound mail relay.

Hourly limits by plan

Plan	Messages per domain, per hour
cPanel Reseller Hosting	150
DirectAdmin Reseller Hosting	150
Infinity Hosting	150
Infinity+ Hosting	150
Premium Hosting — Pro	150
WebGee Workspace	250
Premium Hosting — Business	250
Premium Reseller	250
Premium Hosting — Enterprise	350
Premium Hosting — Platinum	500

There is no daily limit. There is a 25% overage buffer: messages above the hourly threshold are queued rather than rejected outright, up to that margin. Beyond it, outbound attempts are rejected.

What counts towards the limit

Everything the account sends, not just mail from a mail app:

Messages sent from mail apps and webmail.
Mail sent by PHP scripts and applications, including contact forms, order confirmations and password resets.
Mailing list traffic.

A busy WooCommerce store can consume a meaningful share of the limit on transactional mail alone, before anyone sends a message by hand.

Automatic monitoring

250 or more recipients in one hour triggers a notification, and may trigger a block.
More than 500 messages in 24 hours triggers a notification, and may trigger a block.

These thresholds exist to catch compromised accounts, which is what sending spikes usually indicate. If you receive one of these notices and were not sending in bulk, treat it as a possible compromise: change the mailbox password and check Track Delivery in cPanel.

Marketing email is not permitted

WebGee's mail facilities must not be used for email marketing. Shared mail infrastructure is not suitable for campaigns, and sending them will get the account blocked.

Use a service built for it — Mailchimp, SendGrid, Brevo or similar. They handle list management, unsubscribe handling and bounce processing, all of which are required for campaigns to be delivered at all.

Transactional mail from your application is fine within the limits above. The distinction is whether the recipient asked for that specific message.

If you are hitting the limit

Move campaign mail to a marketing service.
Route your application's mail through a third-party SMTP relay, which keeps it off the shared quota — see Why PHP mail fails.
Move to a plan with a higher limit.