Short answer: Most DirectAdmin delivery faults trace back to three settings. Forwarder loops: since 1.693 the Exim configuration discards the looping leg instead of bouncing, so remove the return forward and rebuild the Exim configuration. Send limits: the daily cap lives in /etc/virtual/limit or /etc/virtual/limit_USER, usage in /etc/virtual/usage/USER, and since 1.702 every recipient counts, local ones included. Hosted domains with external mail: 1.703 checks MX records by default (FORCED_MX_DNS_CHECK). See which router and transport a recipient gets with exim -bt user@example.com. (Reviewed October 2026.)
Applies to DirectAdmin 1.693 and later with the CustomBuild-managed Exim configuration (send-limit changes from 1.702, FORCED_MX_DNS_CHECK and SEND_LIMIT_COUNT_RECIPIENTS from 1.703; Exim 4.99.x)
Most DirectAdmin mail complaints reduce to three mechanisms: a forwarder that sends mail back to where it came from, a user hitting the daily send limit without knowing what counts against it, and mail for a locally hosted domain that is supposed to be delivered elsewhere. Each one leaves a distinct trace in /var/log/exim/mainlog, and each has a configuration knob that changed in the 1.69x and 1.70x releases. This guide takes them in turn.
Table of Contents
Forwarder loops
A loop forms when sales@example.com forwards to team@partner.example and that address, or a rule at the recipient, forwards back. Before 1.693, a forwarding loop between addresses on the server made Exim send a bounce back to the sender even though the message had been delivered. 1.693 changed the Exim configuration to ignore forwarder loops and deliver to all the remaining addresses. A loop that passes through another server is still ended by Exim’s own received_headers_max check (default 30 Received: headers), which abandons delivery and returns an error.
The symptom in the log is a line ending with the loop-protection reason, or, on unpatched configurations, a rapid sequence of deliveries for one message ID. Find them by counting deliveries per message:
grep '=>' /var/log/exim/mainlog | awk '{print $3}' | sort | uniq -c | sort -rn | head
A message ID with dozens of deliveries is a loop. Identify the forwarder from /etc/virtual/example.com/aliases and either remove the return leg or replace the forward with a copy-and-keep configuration on the user’s forwarders page, which prevents the round trip.
Confirm DirectAdmin is on 1.693 or later and check for pending CustomBuild updates, then rebuild the Exim configuration:
da build versions
da build exim_conf
Rebuilding exim.conf through CustomBuild pulls the current configuration set, which includes the loop check.
Send-limit counting
Each user has a daily outbound limit set by the package and stored in /etc/virtual/limit (the default) or /etc/virtual/limit_USER for an override. The count is kept per user in /etc/virtual/usage/USER and reset daily. What surprises administrators is what increments it: every recipient counts, not every message (since 1.702 local-to-local mail counts too; 1.703 adds the SEND_LIMIT_COUNT_RECIPIENTS macro to exclude it), and forwarded mail counts against the account that owns the forwarder. A newsletter to two hundred addresses uses two hundred of the limit; a forwarder that receives a hundred messages a day and passes them on uses a hundred more.
When the limit is hit, Exim rejects further submissions with a message naming the limit, and the log shows the check_limits result. Inspect and, if justified, raise for one user:
cat /etc/virtual/limit
cat /etc/virtual/usage/USER
echo 2000 > /etc/virtual/limit_USER
A user who hits the limit unexpectedly is often compromised. Before raising anything, count the recipients per sender in the log for the day and look at the subject lines; our find the source of outgoing spam guide describes the same investigation and the Exim queries carry over almost unchanged.
Note that DirectAdmin 1.702 moved send-limit counting from the Exim routers to the ACL stage, so over-limit mail is rejected before it enters the queue. If you added a smarthost router by hand in /etc/exim.routers.pre.conf following an older recipe, compare it with the current smarthost recipe in the DirectAdmin documentation, which no longer contains a check_limits condition.
Outbound MX lookups for local domains
A domain hosted on the server for web but with mail at a third party is a classic misdelivery source. Exim treats any domain listed in /etc/virtual/domains as local and delivers to the local mailbox, so mail from one hosted site to another hosted domain that actually uses an external provider never leaves the server.
1.703 introduced FORCED_MX_DNS_CHECK and enables it by default. With it on, Exim looks up the MX for a local domain before delivering locally and, if the MX points elsewhere, routes the message out over SMTP. This removes the need to manually untick local delivery per domain, at the cost of a DNS lookup per local delivery. It is an Exim macro; if a line in the custom variables file disables it, delete that line to restore the default and rebuild:
grep FORCED_MX_DNS_CHECK /etc/exim.variables.conf.custom
sed -i '/^FORCED_MX_DNS_CHECK /d' /etc/exim.variables.conf.custom
da build exim_conf
The per-domain method still works and is the right choice when only a few domains are external: the user unticks Local mail server on the MX records page, which moves the domain from /etc/virtual/domains into the remote list. External mail with Google Workspace or Microsoft 365 on DirectAdmin covers that path and its DNS.
Common pitfall: the MX check with a broken resolver
With FORCED_MX_DNS_CHECK enabled, every delivery to a hosted domain depends on a working resolver. When lookups time out, Exim’s default router behaviour is to defer the address, so mail for hosted domains queues until DNS recovers. If the server runs a local Unbound resolver, make sure resolv.conf has a fallback entry, and watch for MX lookup errors in the mainlog after any resolver change.
Verify
Send a test from a hosted account to an address at an externally hosted local domain and follow the message:
exim -bt user@external-hosted.example
tail -f /var/log/exim/mainlog
exim -bt prints the router and transport Exim would use; with the MX check working it shows the remote SMTP transport and the external MX host. For the send limit, confirm the usage file resets after midnight and that the user’s counter rises by recipient count on a multi-recipient test. For loops, resend through the forwarder and confirm exactly one delivery per message ID in the log. Our Exim mail queue report run hourly highlights the queue growth that all three faults produce before users report them.
DirectAdmin mail delivery problems at a glance



Official documentation (checked 9 October 2026): DirectAdmin 1.693 changelog: Improved email forwarders loop handling in the Exim configuration · DirectAdmin 1.702 changelog: Sent email limits will count local-to-local emails · DirectAdmin 1.703 changelog: More secure outgoing email delivery; Flexible Exim configuration for not counting local-to-local emails · DirectAdmin docs: Preventing outgoing spam · DirectAdmin docs: Email troubleshooting (Unroutable address) · DirectAdmin docs: Troubleshooting Exim · DirectAdmin docs: Exim smarthost · Exim specification: Main configuration (received_headers_max) · Exim specification: Generic options for routers (pass_on_timeout) · Exim specification: The Exim command line (-bt) · DirectAdmin docs: CustomBuild overview
Related guides: Choosing a VPS for a cPanel or DirectAdmin server in 2026 · Exim 4.99/4.100 on cPanel and DirectAdmin: the 2026 security fixes and what changed for admins · Warm up a new mail server IP or sending domain without landing in spam.
Frequently asked questions
Does the DirectAdmin send limit count forwarded mail against the user?
Yes. Every recipient of every message that passes through the account counts, including messages a forwarder relays on, so a busy forwarder can exhaust a low limit without the user sending anything themselves.
How long does it take for the send-limit counter to reset?
The counter in /etc/virtual/usage/USER is reset daily by DirectAdmin, so a user who hits the limit is blocked until the following day unless an administrator raises the limit or clears the file.
Can I undo this?
Yes. A raised per-user limit is reversed by deleting /etc/virtual/limit_USER, and FORCED_MX_DNS_CHECK is disabled by setting it to no (FORCED_MX_DNS_CHECK = no) in /etc/exim.variables.conf.custom and rebuilding exim.conf with da build exim_conf.
