Custom Email Sending Domain

By default, Luma sends event emails from our own authenticated domains (luma.com and luma-mail.com). With a custom sending domain, your event emails come from your own domain instead—so attendees see mail from [email protected] rather than a Luma address.

A custom sending domain is available on Luma Enterprise plans.

Why Use a Custom Sending Domain

Sending from your own domain makes your event communication look and feel like it comes directly from your organization. It reinforces your brand, builds trust with recipients who recognize your domain, and keeps your event emails consistent with the rest of your company’s mail.

How to Set It Up

Setting up a custom sending domain is a quick, guided process with our enterprise team:

1. Once your Enterprise plan is active, let your Luma contact know the domain you’d like to send from (for example, yourcompany.com), along with the From address and the Reply-To address you want attendees to see.
2. We’ll send you the exact DNS records to add at your domain’s DNS provider. These authenticate Luma to send on your behalf so your mail lands reliably.
3. Add the records and let us know. We’ll verify they’re live and turn on your custom domain.

Once it’s verified, your event emails send from your domain automatically—there’s nothing else to configure.

DNS and Deliverability

The records we provide handle authentication (DKIM) so your mail is signed in alignment with your domain. To get the best deliverability—and to ensure calendar invites show interactive RSVP buttons in Gmail—your domain should also have a DMARC record:

_dmarc.yourdomain.com → TXT → v=DMARC1; p=none;

If your domain already has a DMARC record, leave it as is—your Luma mail passes under it automatically. For more on email authentication and troubleshooting, see Email Delivery Troubleshooting and Troubleshooting Google Calendar Invites.

How Authentication Works

For the security-minded, here’s how sending works under the hood.

Luma sends your event emails through Amazon SES, signed with a 2048-bit RSA DKIM key. The signature is aligned to your domain—its signing domain (d=) matches your sending domain—which is what lets your mail pass DMARC. That’s why publishing a DMARC record (above) is all that’s needed, and you don’t have to add an SPF record for Luma.

During setup we give you two CNAME records, each with a selector unique to your domain, pointing at public keys we host (dkim1.luma-email.com and dkim2.luma-email.com). Only one is active at a time—the second is there for redundancy and so we can rotate keys without you having to change your DNS again. The unique selectors also mean these records won’t collide with any DKIM setup already on your domain.

You keep control of your domain throughout: we only ask you to add the CNAME records we provide—never a private key, and no delegating your domain to us.