Help

Send reminders from your own domain

By default your reminders arrive as "Your Business via Mugavi". If you connect a domain you own, they arrive from an address like billing@yourcompany.com instead. This takes about ten minutes of your time, plus however long your DNS host takes to publish.

What you need

• A domain you own, such as yourcompany.com, and a login to wherever its DNS is managed (your registrar, Cloudflare, or your web host).
• A Mugavi account with email sending turned on. If it is not, the Send settings panel says so and the Connect button stays off.

1. Connect the domain

1. Open Dashboard, then Dunning, then Send settings, and find "Send from your own domain".
2. Type your domain (yourcompany.com is fine, so is a full web address; we strip the rest). Subdomains such as mail.yourcompany.com work too.
3. Choose the part before the @. It defaults to billing. Names like admin, security, postmaster and noreply are not allowed.
4. Press Connect domain. Mugavi registers the domain with our email provider, Resend, and shows you a table of DNS records.

Each domain can be connected to one Mugavi account, and each account can have one domain at a time. Remove it first if you want to switch.

2. Add the records Mugavi shows you

Copy each row from the table into your DNS host exactly as shown. The values are generated for your domain, so use the ones on your screen and not examples from elsewhere. Typically the table holds:

• DKIM. A TXT record that lets receiving mail servers check a signature on every message. It proves the mail was authorised by you.
• SPF. A TXT record, plus an MX record, on a "send" subdomain. SPF lists which servers may send for the domain. Because it sits on the subdomain, it does not replace or conflict with the SPF record your normal mail already uses on the main domain.

If Resend changes what it asks for, the table in your dashboard is always the source of truth.

3. Check verification

Press Check verification. Publishing DNS can take a few minutes or most of a day, so "waiting for DNS" is a normal answer, not an error. Each record in the table shows its own status. Come back and press the button again later.

Until the domain shows Verified, nothing is sent from it. Reminders keep going out as "Your Business via Mugavi" and the Dunning page shows a warning saying so, so you are never left guessing where your mail is coming from. If the status turns to Failed, one of the records is wrong or missing; compare each row against what your DNS host has.

4. Add a DMARC record (recommended)

DMARC tells receiving servers what to do with mail that claims to be from your domain but fails SPF and DKIM. Gmail and Yahoo expect it from anyone sending to many people. It is separate from the table above and is not needed for verification. Add one TXT record:

Type:  TXT
Name:  _dmarc
Value: v=DMARC1; p=none; rua=mailto:you@yourcompany.com

p=none only watches and reports, so it cannot block your own mail. The rua address (optional) receives daily summary reports; use a mailbox you read. Once you have run for a few weeks and the reports show only your own mail passing, you can tighten it to p=quarantine. Mugavi does not change your DMARC policy for you.

What changes once it is verified

• Reminders go out with your business name as the sender, from the address you chose on your domain.
• Each step in a sequence can use a different name or a different address on the same domain (for example accounts@ first, a person's name last).
• Replies still come into your Mugavi Inbox. We do not connect to your own mailbox.
• Removing the domain at any time sends reminders back to the "via Mugavi" sender.

When an email does not get through

If a message bounces because the address does not exist, or the recipient marks it as spam, Mugavi stops sending reminders to that customer and the reminder shows as failed. A temporary bounce (a full mailbox, for example) is recorded as failed, but reminders to that customer continue. If reminders failed in the last 14 days, the Dunning page tells you.

Common mistakes

The domain name appears twice.

Some registrars add your domain to the Name field for you. If the table says resend._domainkey and you end up with resend._domainkey.acme.com.acme.com, enter only resend._domainkey.

A long DKIM value is cut or has extra quotes.

Paste the whole value on one line. Some registrars add the quotes themselves, so do not type your own.

A proxy is switched on.

If your DNS host is Cloudflare, set any record from the table to "DNS only" (grey cloud).

You are using a free mailbox domain.

gmail.com, outlook.com, yahoo.com and similar cannot be connected. You need a domain you own and can add DNS records to.

You already have a DMARC record.

Keep it. A domain can only have one record at _dmarc, and two make both invalid.

Good authentication helps your mail get judged on its own merits. It does not guarantee inbox placement, and we cannot promise it. Stuck? Write to hello@getcollectly.app or see how we handle your data.