Email Deliverability in Japan: Carrier Domains, Gmail, and Getting Into the Inbox

Email deliverability in Japan is a two-front problem: the global rules that Gmail enforces everywhere, plus a uniquely Japanese layer — mobile carrier domains (docomo.ne.jp, au.com/ezweb.ne.jp, softbank.ne.jp) whose filtering is stricter, less transparent, and partly controlled by user-side allow/deny lists. Getting into Japanese inboxes means full authentication (SPF, DKIM, DMARC), compliance with Gmail's bulk-sender requirements, carrier-aware list hygiene, and a real sunset policy. Here is the complete playbook.

Japan's inbox landscape

A typical Japanese consumer list breaks into three groups with different behavior:

Gmail

Gmail is the dominant personal mailbox for Japanese smartphone users, and it behaves in Japan as it does everywhere: engagement-driven filtering, the Promotions tab, and — since 2024 — hard requirements for senders above roughly 5,000 messages per day to Gmail addresses.

Yahoo! JAPAN Mail

Yahoo! JAPAN Mail (yahoo.co.jp) remains a large legacy mailbox provider. Note that Yahoo! JAPAN is operated separately from the US Yahoo (now Yahoo Inc.), so yahoo.co.jp is not automatically covered by statements about "Yahoo's" sender requirements — but its filtering direction is similar: authentication and low complaint rates are the baseline, and it supports its own spam-reporting and filtering systems.

Carrier domains

Addresses issued by the three mobile carriers date from the pre-smartphone era, when email-to-the-handset was the primary mobile channel. They persist on Japanese lists — skewing to older demographics and long-tenured customers — and they are the segment most likely to silently swallow your mail.

Carrier domains and how they filter

Domain	Carrier	Behavior to know
docomo.ne.jp	NTT docomo	Aggressive default spam settings; users maintain domain-level receive/deny lists; mail from unauthenticated or unknown senders is frequently dropped without a bounce
ezweb.ne.jp / au.com	au (KDDI)	Two active domains for the same carrier; similar user-side allow-list system; strict URL and sender filtering options users can enable
softbank.ne.jp / i.softbank.jp	SoftBank	softbank.ne.jp is the carrier-mail domain, i.softbank.jp the smartphone mail domain; both offer user-configurable domain filtering

The user-side allow list (jushin list settei)

The single most Japanese feature of this landscape: carrier users can — and, after years of spam waves, often do — configure their handset to receive mail only from explicitly allowed domains. If your sending domain is not on that list, your mail may be dropped with no bounce and no spam-folder placement; it simply never arrives. The standard countermeasure is to ask for it at signup: display a notice on the signup confirmation screen and in the first message asking docomo, au, and SoftBank users to set their device to receive mail from your domain. It looks quaint; it measurably reduces silent loss.

Silent drops distort your metrics

Because carrier filtering often discards rather than bounces, your ESP can report a successful delivery that never reached a human. If your carrier-domain segment shows near-zero opens and clicks across months, assume filtering — not disinterest — and treat those addresses accordingly rather than continuing to send into the void.

Rendering constraints

Carrier mail apps are far more limited than Gmail's. Keep sends to carrier domains simple: modest image weight, no heavy CSS, a clear text fallback, and short subject lines that survive truncation. If your design system leans on large hero images, test the degraded version — our Japanese email design guide covers layouts that hold up across clients.

Authentication: the non-negotiable baseline

1. SPF: publish a record authorizing your ESP's sending IPs for your sending domain.
2. DKIM: sign with your own domain (in Klaviyo, set up a dedicated/branded sending domain so DKIM aligns with your From address, rather than sending on shared defaults).
3. DMARC: publish at least a p=none policy with reporting, confirm alignment, then move toward quarantine/reject as reports come clean. Gmail's bulk-sender rules require a DMARC record at minimum.
4. Warm up: ramp volume gradually on a new domain — weeks, not days — starting with your most engaged segment so early signals are positive.

Carrier filters are opaque, but authenticated, aligned mail from a consistent domain is the common prerequisite across every Japanese mailbox provider. Authentication also protects the transactional mail your CRM depends on — see localizing Klaviyo flows for Japan for how the flow layer and infrastructure layer fit together.

Gmail's bulk-sender rules apply to your Japanese list

Since February 2024, Gmail enforces requirements on senders of roughly 5,000+ daily messages to Gmail mailboxes — a threshold many Japan-focused brands cross, given Gmail's local dominance:

1. SPF and DKIM must both pass, with a DMARC policy published and the From domain aligned.
2. One-click unsubscribe (List-Unsubscribe headers) is required on marketing mail, with opt-outs honored within two days.
3. User-reported spam rates must stay below 0.3% in Google Postmaster Tools — and ideally well under 0.1%.
4. Sending domains must have valid forward and reverse DNS.

Register your domain in Google Postmaster Tools and watch the spam-rate and domain-reputation panels monthly. For Japanese lists specifically, complaint spikes usually trace to two causes: sending to stale carrier-era addresses re-permissioned onto a new platform, and sudden cadence jumps around sale periods.

List hygiene and sunset policies

Why Japan makes hygiene harder

Japanese lists age in a specific way: carrier addresses abandoned when users migrated to smartphones and Gmail, mistyped domains (docomo.co.jp instead of docomo.ne.jp), and — a genuinely local quirk — legacy carrier addresses that were technically invalid under RFC rules (such as dots directly before the @) yet functioned on carrier systems. Validation tools and strict ESPs can disagree with reality on these; handle bounces empirically rather than assuming a validator is right.

Build the sunset policy

A sunset policy is the rule set that stops you from mailing people who have stopped engaging — the single biggest lever on complaint and reputation metrics:

1. Define engagement on clicks and site activity, not opens alone — privacy features inflate open data, and carrier-domain silent drops suppress it.
2. Segment by recency: for example, engaged within 90 days, 90–180 days, and 180+ days (tune to your purchase cycle).
3. Send full cadence only to the engaged core; reduce frequency to the middle band.
4. Run a short re-engagement series to the lapsed band — in Japan, a concrete coupon or a LINE-switch invitation outperforms sentimental "we miss you" copy; some of your quiet email subscribers are active on LINE, which is one more reason to run both channels (LINE vs email in Japan).
5. Suppress non-responders entirely. Shrinking the list this way almost always improves revenue per send and inbox placement together.

Monitoring and diagnosis

Work from evidence, not vibes:

1. Break every campaign report down by domain group — Gmail, yahoo.co.jp, the three carriers, other — so a carrier-specific problem is visible instead of averaged away.
2. Watch bounce codes: carrier bounces are terse, but a rising "unknown user" rate on a carrier segment means dead addresses; throttling-style deferrals mean you are sending too much too fast to that domain.
3. Seed-test major sends to real accounts at Gmail, Yahoo! JAPAN, and, if you can maintain them, carrier addresses.
4. Keep collection quality high upstream — confirmation screens and double opt-in catch carrier-domain typos at the source, which is cheaper than cleaning them later (see list growth in Japan).

A 30-day deliverability playbook

1. Week 1: audit SPF/DKIM/DMARC, set up a branded sending domain if you are on shared defaults, and register with Google Postmaster Tools.
2. Week 2: segment the list by domain group; quantify the carrier share and its engagement; add the receive-list instruction to signup and welcome messages.
3. Week 3: define and implement the sunset segments; move to click-based engagement definitions; enable one-click unsubscribe headers.
4. Week 4: launch the re-engagement series to lapsed segments, suppress non-responders, and set a monthly review of spam rate, domain reputation, and per-domain-group engagement.

FAQ

Are carrier email addresses still worth mailing?

Yes, selectively. They over-index on older and long-tenured customers who can be highly valuable. Mail the engaged ones, ask them to allow-list your domain, and sunset the silent ones — the segment is worth keeping, but not worth mailing indiscriminately.

Why do my emails to docomo.ne.jp disappear without bouncing?

docomo's filtering commonly discards suspect mail rather than rejecting it, and many users run domain-level allow lists that drop everything unlisted. Verify your authentication, keep volume steady, and instruct docomo subscribers at signup to add your domain to their receive list.

Do Gmail's bulk-sender rules apply to a Japan-only brand?

Yes. The rules attach to volume sent to Gmail mailboxes regardless of sender geography, and Gmail is the leading personal mailbox in Japan — most Japan-focused senders of meaningful size are covered.

What spam-complaint rate should I target?

Stay below 0.3% in Google Postmaster Tools as the hard ceiling, and treat under 0.1% as the working target. Sustained rates near the ceiling degrade inbox placement even without a formal block.

Is a shared Klaviyo sending domain good enough for Japan?

It works at low volume, but a branded sending domain with aligned DKIM and your own DMARC policy is the standard for anyone sending seriously — it is required behavior under Gmail's rules at scale, and it gives carrier filters a consistent identity to trust.

---

Yulie is a Klaviyo partner agency based in Japan. We set up authentication, carrier-aware segmentation, and sunset policies for overseas Shopify brands sending to Japanese lists. Get in touch and we will reply within one business day, in English, no meetings required.