Enterprise Mail Security & Deliverability

How to Verify Maileroo Domains When You Already Use Mailcow or TwaMeHi

Maileroo's default onboarding instructions can break your incoming mail and DMARC if you already have a private mail server. Here is the exact 3-step action plan to verify your domain safely.

Published by TwaMeHi Systems • Verified Protocol Architecture
Quick Answer: When verifying a domain in Maileroo that is already connected to Mailcow or TwaMeHi, you must ignore Maileroo's MX and DMARC recommendations. Only edit your existing SPF to include Maileroo, and add the DKIM and CNAME tracking records.

When you sign up for a bulk email delivery service like Maileroo, their onboarding wizard gives you a list of DNS records to add. If you are starting from scratch, those instructions are fine.

But if you already have a functioning private mail server (like Mailcow or the TwaMeHi suite), blindly following Maileroo's default instructions will cause a disaster. Adding their MX records will break your incoming email, and adding their DMARC record will conflict with your existing strict security policies.

Here is your exact, step-by-step action plan to verify your Maileroo domain safely without breaking your existing mail flow.

1. The Merge (Edit your existing SPF)

Your SPF record tells the world which servers are allowed to send email on your behalf. You can only have one SPF record per domain. Maileroo tells you to add a new one, but you must merge theirs into yours instead.

You currently have this TXT record in your DNS (for your Mailcow server):

v=spf1 mx ip4:169.58.112.90 ~all

Edit that existing record and change the value to include Maileroo:

v=spf1 mx ip4:169.58.112.90 include:_spf.maileroo.com ~all

2. The Additions (Create 2 New Records)

Maileroo requires two completely new records to sign your emails and track clicks. Note that Maileroo's dashboard sometimes displays confusing hostnames (like mta._domainkey.yourdomain.com). In your DNS provider (like Cloudflare or GoDaddy), you only need to enter the short name.

Add New Record #1 (DKIM)

  • Type: TXT
  • Name/Host: mta._domainkey
  • Value: (Copy the long v=DKIM1... string directly from your Maileroo dashboard)

Add New Record #2 (Custom Tracking)

  • Type: CNAME
  • Name/Host: click
  • Value: click.maileroo.net

3. What to Ignore (Skip these entirely)

This is the most critical step. Maileroo will show you MX and DMARC records on their setup page. Ignore them completely.

  • Ignore the MX Records: Maileroo handles your outgoing bulk mail. Your Mailcow server handles your incoming mail. Keep your incoming mail flowing to your own server. Maileroo will still verify your domain even if you skip their MX records.
  • Ignore the DMARC Record: Your Mailcow/TwaMeHi setup already has an excellent, strict DMARC record set up (e.g., v=DMARC1; p=quarantine;...). If you add Maileroo's DMARC record, the two records will conflict, causing catastrophic delivery failures across the board. Keep your existing one!

Once you make these specific changes, wait 5 to 10 minutes for DNS propagation, then click Verify in Maileroo. Your domain will activate perfectly, and your primary business email will remain fully protected.