I want to use Lolipop email on a domain I manage through Cloudflare. But my web app is hosted on Vercel, and the authentication emails are automated with Supabase and Resend.

Even in a situation like this, you can point the mail server alone to Lolipop by adding MX and TXT records (SPF, DMARC, DKIM). I just did exactly that a little while ago.

With the Light plan I’m currently subscribed to, Lolipop is an absolute steal: 350GB of disk space, up to 200 custom domains, 300 subdomains per custom domain, unlimited email addresses, and a 3-year contract for 9,500 yen (around 300 yen per month).

If you wanted to use custom domain email through Google Workspace, it’s number of email addresses × per-person price (Starter 800 yen, Standard 1,600 yen, Plus 2,500 yen, with 50% off for the first 3 months), which gives you a sense of how remarkable Lolipop’s custom domain email is. And above all, it’s a Japanese brand you can trust with peace of mind.

If you want to make two-factor authentication mandatory for accessing email, or if you want to make serious use of organization-oriented features, Google starts to have the edge. But Google’s collaboration features are usable for free, and if the only exchanges you have over email are ones you wouldn’t mind leaking, there’s probably no need to worry excessively.

As for the specific setup: first, on the Lolipop side, register the domain you want to use. Because the DNS points to Cloudflare (normally, pointing only the MX record isn’t something they anticipate), a warning message appears, but go ahead and confirm anyway.

Next, configure the following in Cloudflare:

Type: MX / Name: @ / Value: mx01.lolipop.jp / Priority: 10 / TTL: 3600

SPF — Type: TXT / Name: @ / Content: v=spf1 include:_spf.lolipop.jp ~all

Optionally, if needed:

DMARC — Type: TXT / Name: _dmarc / Content: v=DMARC1; p=none;

DKIM — Type: TXT / Name: default._domainkey / Content: [key string]

Web-facing records like A or CNAME can be left as they are (in my case, Vercel), no problem.

Since Lolipop supplies DKIM by default, apparently if you use “Show original” on an email sent from there and DKIM=PASS, you’re fine.

In my case, I had Lolipop email on the main domain example.com and Supabase and Resend on the subdomain auth.example.com, so having two SPF records was no problem. But if you’re using Lolipop and Resend together on the same domain, you need to combine them into a single SPF record.

SPF — Type: TXT / Name: @ / Content: v=spf1 include:_spf.lolipop.jp include:amazonses.com include:resend.com ~all

That’s the idea.

Once the Cloudflare side is done, it’s finally time to create email addresses in Lolipop. You can make as many as you like, such as yourname@example.com or hello@example.com. Try sending and receiving, and if it works, you’ve succeeded.

If, compared to Gmail or iCloud, you’re uneasy about the lack of multi-factor authentication support and being able to get into the web mailer or IMAP with just a password, then just go ahead and use PGP. The biggest hurdle is that the other party also has to have generated a PGP public/private key pair and have the cryptographic literacy to use it.

2026-05-13 04:53