Updated: 9 November 2026 · Applies to: DirectAdmin (Evolution skin, current releases; settings and defaults from DirectAdmin documentation)

To set an email sending limit in DirectAdmin, open E-mail Manager > E-mail Accounts, open the mailbox’s Change Limit/Quota option (or fill in Daily Send Limit when you create the account) and enter the number of emails the mailbox may send per day. DirectAdmin has two daily limits: one per mailbox (200 by default on current versions) and one for the whole DirectAdmin user account, which caps the total of all its mailboxes and scripts. When a limit is reached, further sending stops until the daily count resets.

A send limit caps the damage if a mailbox password is stolen and used for spam, and it keeps one busy mailbox from using up the whole account’s allowance.

1. Set the limit for one mailbox (user level)

  1. Log in to DirectAdmin (usually https://your-server:2222). See logging in to your DirectAdmin account.
  2. Open E-mail Manager > E-mail Accounts.
  3. For a new mailbox, start creating the account. The Create Mail Account page has a Daily Send Limit field next to E-mail Quota (MB), with a hint showing the highest value you may enter.
  4. For an existing mailbox, find it in the list and choose Change Limit/Quota from its options.
  5. Enter the number of emails per day, or select Max to use the highest value allowed. Since DirectAdmin 1.707 you have to select Max on purpose; leaving the field blank no longer does this.
  6. Save. According to DirectAdmin, users can see each mailbox’s effective limit and how many emails it has sent.

The value you can enter is capped by the server’s per-mailbox maximum, and every mailbox together is still capped by your account’s overall limit. If you cannot change the value, the administrator has turned off user_can_set_email_limit (it is on by default); ask them to change the limit for you.

2. Set the limits as the server administrator

On your own VPS or dedicated server with DirectAdmin, you control both limits.

Per-mailbox limit (all mailboxes)

Change it in Administrator Settings > E-Mail, or from SSH. To see the current value:

da config-get max_per_email_send_limit

To set it, for example to 300 emails per mailbox per day:

da config-set max_per_email_send_limit 300

According to DirectAdmin, da config-set reloads DirectAdmin automatically since version 1.710 (add --no-reload to skip that). The default is 200, and 0 means unlimited, which DirectAdmin does not recommend. Since version 1.676 this setting replaces the old /etc/virtual/user_limit file, which is no longer read; old guides that edit that file do nothing on current versions. If you edit configuration files by hand instead, DirectAdmin says to apply them with:

da taskq --run 'action=apply-email-per-mailbox-limits'

To give one user a different per-mailbox maximum, set max_per_email_send_limit in that user’s user.conf, or open Show All Users, select the user and edit their details.

Per-user limit (all mailboxes and scripts of one account)

This is a daily cap on everything one DirectAdmin user sends: all mailboxes plus scripts. The server-wide value is in /etc/virtual/limit; DirectAdmin’s own example uses 200:

echo 200 > /etc/virtual/limit

A per-user override lives in /etc/virtual/limit_username (replace username with the DirectAdmin user name). The max_user_send_limit option (default -1, meaning take the value from /etc/virtual/limit) sets the highest value a Reseller can give.

Let Resellers set limits

Resellers cannot change their users’ mail limits by default. Enable it with:

da config-set reseller_can_set_email_limit 1

The Reseller then finds the setting under List Users, the user, then E-Mail Limit. Resetting a user’s sent count is a separate option, reseller_can_reset_email_count, also off by default.

3. What happens when a limit is reached

  • With the default notify_email_on_per_email_limit=1, DirectAdmin emails the mailbox to say its per-mailbox limit has been reached.
  • According to DirectAdmin, with current Exim versions a mailbox over its limit gets an invalid password error when it tries to send through SMTP authentication. If a mail app suddenly says the password is wrong for sending only, while receiving still works, check the send count before you reset the password.
  • Sending works again after the daily count resets, or when the administrator raises the limit.
  • default_email_notify_limit (1000 by default) only sends the administrator a notice; it does not block anything.

If an account hits its limit without a reason you know of, treat it as a possible compromise: change the mailbox password (see change an email password in DirectAdmin), look for unknown scripts in the website, and check the mail logs (log file locations in DirectAdmin). DirectAdmin also writes per-user usage to /etc/virtual/usage, which helps spot the account that is sending more than usual.

SMTP rate limits and “daily relay limit exceeded” errors

Almost every mail provider limits sending, for the same reason DirectAdmin does. Messages such as “daily SMTP relay limit exceeded for this customer”, “quota exceeded” or an SMTP 4xx or 5xx reply that mentions a rate or limit mean that the server you send through has stopped accepting mail from your account for now. The limit belongs to that server, not to your mail app, so changing settings in Outlook or your website will not lift it. Wait for the reset, ask the provider for a higher limit, or send less.

For newsletters and bulk mail, use a dedicated email marketing service rather than a hosting mailbox, so a large send cannot block your normal mail. For website mail, send through SMTP authentication on port 587 (see SMTP port numbers explained).

Official documentation: DirectAdmin: Preventing outgoing spam, All directadmin.conf values and DirectAdmin 1.676 changelog.

Related services

Server management

on-demand administration, hardening, migrations and monitoring.

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Was this answer helpful?

Still stuck? Open a ticket