Set Up Email Forwarding on DirectAdmin

Email forwarding automatically relays incoming messages from one address to another — without manual intervention. For example, configure [email protected] to forward every email to [email protected], and you'll receive all business emails in Gmail without logging into a separate webmail client.

DirectAdmin supports flexible forwarder rules: single destination, multiple destinations, and keeping a copy in the original mailbox at the same time.

Email Forwarder vs Email Account — Which One, When?

Before you configure a forwarder, it's worth understanding the difference between an Email Forwarder and an Email Account, because they solve different problems. Choosing the wrong one is the most common reason people end up with lost messages or an address they can't open in webmail.

• Email Account (real mailbox): Has dedicated storage on the server. Messages are kept in an inbox you can open through Roundcube webmail, or via IMAP/POP3 in Outlook, Apple Mail, or your phone. Best for anyone who needs to retain email permanently and work with it directly on the server.
• Email Forwarder: Doesn't require any storage. It acts as a relay point — incoming mail is immediately passed on to another destination (such as Gmail). If there's no companion mailbox, nothing is stored on the server at all.

The simple rule: if you need to store and read mail on the server itself, use an Email Account. If you want every message consolidated into a Gmail or primary inbox you already use, use a Forwarder. And if you want both at once, create the Email Account first, then add a forwarder that also lists the address itself as a destination — that way you keep a copy and relay at the same time.

Forwarder vs Alias — Which to Use?

Both route email to a different mailbox, but they work differently:

• Alias: An extra name for an existing mailbox within the same domain. No separate storage, can't forward outside the domain.
• Forwarder: Routes email to any address — including external addresses like Gmail. Can exist with or without a local mailbox.

If you need to forward to Gmail or any external address, use a Forwarder, not an Alias.

Forwarder vs Catch-All vs Alias — Which to Pick

These three are often confused because all of them "redirect" mail in some way, but their scope differs significantly. The table below makes it clear which to use in each situation:

In short: use a Forwarder when you know the exact destination and need to send outside the domain; use a Catch-All as a safety net that captures any mail sent to a name that doesn't exist (but expect more spam); and use an Alias when you simply want to merge info@, hello@, and admin@ into one mailbox. The alias is the lightest option and never hits SPF problems because the message never leaves your domain.

Creating an Email Forwarder in DirectAdmin

1. Log in to DirectAdmin → Email Manager → Forwarders
2. Click Add Forwarder or Create Forwarder
3. Fill in the details:
   • Forward from: the local part of the source address (before @), e.g., contact
   • Forward to: the destination email address, e.g., [email protected]
4. Click Create — the forwarder is active immediately

Examples

# Basic forwarder
Forward from: contact
Forward to:   [email protected]
→ Emails to [email protected] go to [email protected]

# Forward to a team (multiple people receive the same email)
Forward from: support
Forward to:   [email protected]
Forward to:   [email protected]
→ Every support email reaches both Alice and Bob

Forwarding to Multiple Recipients

To deliver the same email to several people simultaneously:

1. In Email Manager → Forwarders, edit the source address
2. Add each destination address on a separate line
3. Or create multiple forwarder entries for the same source address pointing to different destinations

Real-World Example: Forwarding sales@ to a Whole Team

To make this concrete, suppose your business has a three-person sales team and you want every email sent to [email protected] to reach all of them at once — while also keeping a central copy on the server for later reference. Here's exactly how you'd set it up:

1. Create an Email Account [email protected] with a real mailbox first (this holds the central copy)
2. Go to Email Manager → Forwarders → Add Forwarder and set "Forward from" to sales
3. Add each teammate's address (plus the address itself to keep a copy) on separate lines

# Forwarder: [email protected] → 3-person team + keep a copy
Forward from: sales
Forward to:   [email protected]
Forward to:   [email protected]
Forward to:   [email protected]
Forward to:   [email protected]    # keep a copy on the server
→ Every email to sales@ reaches all three people and stays in the central inbox

This pattern works well for small teams where everyone needs to see customer email simultaneously. Once the team grows beyond 5–10 people, consider moving to a proper mailing list or shared mailbox instead — forwarding to too many destinations makes the mail server work harder and raises the risk of being flagged as spam at the receiving end.

Keep a Copy While Forwarding

You can forward to Gmail and retain a copy on the server for backup or audit purposes:

1. Create a real Email Account (with a mailbox) for [email protected]
2. Go to Forwarders → create a forwarder for contact
3. Set one destination to your Gmail address
4. Add a second destination of [email protected] (the same address) to keep the copy

Reply from Your @Domain Address in Gmail

After setting up forwarding you'll receive emails in Gmail, but replies will show your Gmail address by default. To reply as [email protected]:

1. Gmail → Settings → Accounts and Import → Send mail as
2. Click Add another email address
3. Enter your name and [email protected]
4. Google sends a verification email to that address — because your forwarder is active, it will arrive in your Gmail
5. Click the verification link
6. When composing, choose the @domain address from the "From:" dropdown

SMTP Configuration for Gmail "Send mail as"

# Gmail → Settings → Accounts and Import → Add another email address
SMTP Server: mail.yourdomain.com
Port: 587 (STARTTLS)  or  465 (SSL/TLS)
Username: [email protected]
Password: the password for this DirectAdmin email account

Troubleshooting Email Forwarding

Forwarded Emails Going to Gmail Spam

This is common. When an email is forwarded, it arrives at Gmail from your mail server's IP rather than from the original sender's server. This can cause SPF to fail at Gmail:

• Ensure your domain has a valid SPF record that includes your hosting server
• Enable DKIM on DirectAdmin — DKIM signatures survive forwarding and help establish authenticity
• Consider using Gmail's POP3 fetcher as an alternative (Gmail actively downloads emails from your mailbox rather than receiving forwards)

Forwarded Email Not Arriving

• Verify the destination address is typed correctly — no extra spaces or typos
• Confirm the forwarder is still listed in DirectAdmin → Email Manager → Forwarders
• Check the DirectAdmin Mail Queue for delivery errors
• The destination provider (Gmail, Outlook) may have blocked email from your server's IP — check Google Postmaster Tools

Email Forwarding and Deliverability

Forwarding can affect deliverability because the forwarding server re-sends the message with a different IP than the original sender, which may fail SPF checks at the destination. Best practices:

• Configure DKIM on your DirectAdmin server — DKIM signatures are preserved through forwarding
• Set up DMARC with p=none initially to monitor authentication results
• If forwarded emails consistently land in spam, switch to Gmail POP3 fetching as an alternative

Why Forwarded Email Hits Spam (SPF/SRS) and How to Fix It

The single most frustrating forwarding problem is "messages I forward to Gmail keep landing in spam." The root cause is email authentication at the destination — particularly SPF. Here's why it happens and how to fix it:

Why SPF Fails When Forwarding

SPF (Sender Policy Framework) checks whether "the IP that sent this message is authorized by the sending domain." When someone sends mail from [email protected] to [email protected], and your forwarder relays it to Gmail, Gmail sees that the message arrived from your mail server's IP — but the Envelope From is still example.com, whose SPF record does not authorize your IP. The result: SPF fails.

SRS (Sender Rewriting Scheme) Is the Fix

SRS solves this by rewriting the Envelope From at forwarding time so it points back to your domain — for example srs0=xxxx=yourdomain.com. Now when Gmail checks SPF, it checks against your domain (which already authorizes your own IP), so SPF passes. AsiaGB's mail server supports forwarding, and when DKIM/SPF are configured correctly, forwarded mail authenticates far more reliably.

• DKIM matters more than SPF when forwarding: DKIM validates a signature embedded in the message itself, independent of the sending IP, so it doesn't break on forwarding — always enable DKIM in DirectAdmin.
• Don't forward mail that's already spam: if the source is spam, forwarding won't improve it and may hurt your server's IP reputation.
• Check your DMARC reports: verify whether forwarded mail passes DKIM alignment — if it does, the message stays safe even when SPF fails.

FAQ

Can I forward email without creating a mailbox?

Yes. A DirectAdmin forwarder can exist without a corresponding mailbox. The address acts as a pure relay point with no storage. If you also want to be able to log in to Roundcube for that address, you'll need to create a full email account first.

How many destinations can I forward to?

DirectAdmin doesn't impose a hard limit, but forwarding to more than 5–10 destinations per address can slow mail delivery. For large team distributions, consider using a mailing list instead.

Will disabling or deleting a forwarder affect existing emails?

No. Deleting a forwarder only stops future forwarding — all previously delivered messages remain in both the source mailbox (if it exists) and the destination inbox.

Why does my forwarded email land in spam, and how do I fix it?

It's caused by SPF failing at the destination, because the message is sent from your mail server's IP rather than the original sender's. Fix it by enabling DKIM in DirectAdmin (the signature survives forwarding), setting a correct SPF record, using SRS to rewrite the Envelope From, and starting DMARC at p=none to monitor first.

How is a forwarder different from a catch-all?

A forwarder relays only one specific address (such as contact@). A catch-all captures every address that doesn't exist in the domain and sends it to a single destination — useful as a safety net for mistyped names, but it tends to attract more spam.