SMTP quota limits

View the SMTP quota article for details related to this policy. This article lists DreamHost's SMTP quota limitations.

These limits are set for all DreamHost users and cannot be adjusted.

Sending method Recipient per hour Max recipient per message Max message size
SMTP authentication in an email client 100 100 40MB (encoded)
SMTP authentication in atmail Webmail 100 100 40MB
SMTP authentication in a webform 100 100 40MB (encoded)
FTP & Shell users on shared servers. Sending using PHP/CGI scripts. 200 40 40MB (encoded)
FTP & Shell users on VPS or Dedicated servers. Sending using PHP/CGI scripts. Unlimited Unlimited 40MB (encoded)
Announcement Lists Unlimited Unlimited 40MB (encoded)
Discussion Lists Unlimited Unlimited

40MB (encoded)

The limits above are based on the number of RECIPIENTS, not the number of messages. For example, a single email message with 5 recipients would count as 5 towards your sending limit. All recipients in the TO, CC, and BCC fields are counted.

Incoming message limitations

  • The sending limits mentioned above do NOT apply to incoming messages. Just for completeness, here are two incoming message limitations:
  • Maximum message size: This is set to 40MB. Incoming messages over 40MB are bounced.
  • The amount of disk space you've allocated to your mailbox: if your mailbox fills up, it bounces incoming messages. You may not even be able to delete any messages because the server needs some free space in order to work. So, try to avoid allowing your mailboxes fill up. See the Disk Usage Warning article for more information on setting the "Limit total disk usage" and Inbox Archiver article for how to configure "Email me daily" warning messages for your accounts.
  • DreamHost recommends allocating at least 100MB for each mailbox. Attachments in a single email can take up several MB. So just a few large message can fill your inbox.
  • DreamHost recommends enabling the "Email me daily" warning messages option for your accounts. These notifications help you to avoid hitting your disk quota limit.
  • If you have the "Save removed messages" option enabled (which is the default option), those saved messages can eat up your disk space without you ever seeing them. Make sure that you've subscribed to the old-messages folder (or whatever you've configured it to be) so you know what's in there.

Examples of how the limits are implemented

How the message is sent Message and Recipients Outcome
SMTP
Single message with 100 recipients.
  • You reach the maximum sending limit for that hour.
  • After one hour, you can attempt to send more messages.
SMTP
5 messages with 5 recipients each during one hour.
The system counts this as 25 recipients during that hour.
SMTP
100 messages with a single recipient each.
You reach the maximum sending limit for that hour.
SMTP
Single message to 50 recipients, and then within that same hour try to send another message with 55 recipients.
  • The second message FAILS and your account is blocked because it exceeds your sending limit.
  • You must wait for that hour to elapse (from the time you send the first message) before you can attempt to resend the message which could not be sent during the last hour.

What happens when you hit the limits

Once you have reached your hourly sending limit, any message that you attempt to send that exceeds your sending limit causes your account to be blocked immediately. Those messages that exceeded, or attempted to exceed, your sending limit are NOT sent and fail with a "Policy Rejection- Quota Exceeded" error message. Those unsent messages typically remain in your email client's "outbox" so that you can attempt to resend them later.

If you are blocked for exceeding quota, the block will remain in place until at least one hour has passed during which time there have been no further attempts to send mail from the account.

Some email clients (most notably Outlook) will try to send anything in the "outbox" at regular intervals, or at every attempt to send. To have the quota lifted as soon as possible, make sure to remove any message from the outbox, and wait at least an hour before attempting to send again.

However, the mail servers AUTOMATICALLY unblock/reset your account one hour after the first message that was sent. There is no need to contact support when this happens.

Also, if a message that has been successfully sent to a recipient bounces back to you for various reasons, it still counts towards your sending limit. They are not deducted from your sending limit.

Accounts that are blocked repeatedly for attempting to exceed the sending limit are blocked permanently by the system. If this happens to your account, you are required to contact technical support for assistance in order to have your account unblocked. In your support request, please include your email username and email address.

Examples of what can cause you to hit the limits

  • If you have an account set as a forward to any email sent to an another address, those forwarded messages also count towards your sending limit.
  • If you have Keyword Filters on an account that are set to forward any email to another address, those forwarded messages also count towards your sending limit.
  • Auto-responder messages also count toward that account's hourly sending limit.
  • Multiple websites hosted under the same FTP/Shell account that send email all count towards that FTP/Shell account's sending limit.
  • If you use Cron jobs to send email, they count towards the shell account's hourly sending limit. Cron job completion/error notification emails also count.
  • Cron jobs and other scripts/CGI processes that use authenticated SMTP to send email messages are restricted to the sending limit of the address that they use for authentication.
  • Email limits are per email address. This does not mean you can "spread" your bulk/mass email across several email addresses. If you need to send more than 1–2 emails every minute, then you should review the DreamHost anti-spam/bulkmail policy.

See also

Did this article answer your questions?

Article last updated .