6.2 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Recieving Mail thru MXRoute | Trusted receiver | true | 2026-02-15T01:44:15.683Z | markdown | 2026-02-15T01:44:15.683Z |
MXroute Incoming Mail to Mailcow
Overview
Configuration guide for using MXroute to receive incoming mail for your domains and forward to your Mailcow server.
Architecture
Internet → MXroute (receives) → Mailcow (delivers)
This setup allows MXroute to handle incoming mail filtering, spam protection, and then forward clean mail to your Mailcow server.
MXroute Configuration
1. Add Domain to MXroute
- Log into MXroute DirectAdmin panel
- Navigate to Email Accounts → Email Domains
- Add your domain (e.g.,
yourdomain.com)
2. Create Forwarder Accounts
For each mailbox you want to receive mail:
- Navigate to Email Accounts → Forwarders
- Create forwarder:
- Email Address: user@yourdomain.com
- Forward To: user@mail.yourdomain.com (your Mailcow server)
- Enable Discard if no forwarders exist (optional, prevents bounces)
Alternative: Catch-all Forwarder
- Create a catch-all forwarder:
*@yourdomain.com→@mail.yourdomain.com - This forwards all mail to Mailcow regardless of recipient
DNS Configuration
Update MX Records
Point your domain's MX records to MXroute servers:
yourdomain.com → MX 10 arrow.mxroute.com
yourdomain.com → MX 20 eagle.mxroute.com
Note: Check your MXroute account for the correct server hostnames (arrow, eagle, hermes, etc.)
SPF Record
Update SPF to allow MXroute to send on your behalf:
v=spf1 include:mxroute.com -all
If you also send from Mailcow directly:
v=spf1 ip4:192.168.5.16 include:mxroute.com -all
DKIM Records
-
Generate DKIM key in MXroute DirectAdmin:
- Navigate to Email Authentication → DKIM Keys
- Generate key for your domain
- Copy the DNS record
-
Add DKIM TXT record to your DNS:
default._domainkey.yourdomain.com → [MXroute DKIM public key]
DMARC Record
_dmarc.yourdomain.com → v=DMARC1; p=quarantine; rua=mailto:admin@yourdomain.com
Note: Start with p=quarantine for testing, then move to p=reject once confirmed working.
Mailcow Configuration
1. Allow MXroute IP Addresses
Add MXroute server IPs to Mailcow's trusted networks:
-
SSH into your Mailcow server
-
Edit
mailcow.conf:nano /opt/mailcow-dockerized/mailcow.conf -
Add MXroute IPs to
SKIP_CLAMDor trusted networks -
Restart Mailcow:
docker-compose down docker-compose up -d
2. Configure Mailboxes
Create mailboxes in Mailcow for each user:
- Navigate to Mailcow admin → Mailboxes
- Create mailbox:
user@yourdomain.com - Set password and quota
3. Disable Greylisting (Optional)
If you experience delays:
- Navigate to Configuration → Configuration & Details
- Find your domain
- Disable greylisting for MXroute IPs
Testing
1. Test Mail Flow
Send test email from external provider (Gmail, Outlook):
From: test@gmail.com
To: user@yourdomain.com
Expected Flow:
- Mail arrives at MXroute
- MXroute forwards to Mailcow
- Mail appears in Mailcow inbox
2. Check Headers
Review email headers in Mailcow to verify:
Received:headers show MXroute server- SPF, DKIM, DMARC all pass
- No spam flags
3. Monitor Logs
MXroute Logs:
- Check DirectAdmin → Email Logs
- Verify forwarding is occurring
Mailcow Logs:
docker-compose logs -f postfix-mailcow
Look for incoming connections from MXroute IPs.
Example Configuration: gnarlypandaproductions.com
MXroute Forwarders
| MXroute Address | Forwards To |
|---|---|
| admin@gnarlypandaproductions.com | admin@mail.gnarlypandaproductions.com |
| contact@gnarlypandaproductions.com | contact@mail.gnarlypandaproductions.com |
| *@gnarlypandaproductions.com | @mail.gnarlypandaproductions.com |
DNS Records
| Record Type | Name | Value |
|---|---|---|
| MX | @ | 10 arrow.mxroute.com |
| MX | @ | 20 eagle.mxroute.com |
| A | 192.168.5.16 | |
| TXT | @ | v=spf1 ip4:192.168.5.16 include:mxroute.com -all |
| TXT | _dmarc | v=DMARC1; p=reject; rua=mailto:admin@gnarlypandaproductions.com |
| TXT | default._domainkey | [MXroute DKIM key] |
Troubleshooting
Mail Not Being Forwarded
-
Check MXroute forwarder configuration
- Verify forwarder exists in DirectAdmin
- Check destination address is correct
- Review MXroute email logs
-
Verify DNS propagation
dig MX yourdomain.com dig TXT yourdomain.com -
Check Mailcow firewall
- Ensure port 25 is open
- Verify MXroute IPs aren't blocked
SPF/DKIM Failures
-
SPF not passing
- Verify
include:mxroute.comin SPF record - Check for typos in SPF syntax
- Use SPF checker: https://mxtoolbox.com/spf.aspx
- Verify
-
DKIM not passing
- Confirm DKIM record published in DNS
- Verify selector matches (usually
default) - Check DKIM record format (no spaces in key)
Mail Delayed or Bouncing
-
Greylisting delays
- Disable greylisting in Mailcow for MXroute IPs
- Or wait 5-15 minutes for retry
-
Mailbox full
- Check quota in Mailcow
- Increase quota or clean mailbox
-
Spam filtering
- Check Mailcow spam folder
- Whitelist MXroute IPs in Rspamd
MXroute Server Information
Common MXroute Mail Servers
- arrow.mxroute.com
- eagle.mxroute.com
- hermes.mxroute.com
- zen.mxroute.com
Your assigned server: Check MXroute DirectAdmin welcome email or DNS settings
MXroute IP Ranges
Consult MXroute documentation for current IP ranges to whitelist in Mailcow.
Advantages of This Setup
- Spam filtering: MXroute handles initial spam filtering
- DDoS protection: MXroute absorbs mail-based attacks
- Reliability: If Mailcow is down, mail queues at MXroute
- Deliverability: MXroute IPs have good reputation
- Offload processing: Reduces load on your Mailcow server