Suped

Asahi Net sets November 26 DMARC filtering rollout

News
Published 16 Nov 2026
Updated 16 Nov 2026
7 min read
Summarize with
Asahi Net sets November 26 DMARC filtering rollout
17 November 2026 | Australia/Sydney
Asahi Net will enable incoming DMARC filtering by default on 26 November 2026 for @asahinet.jp, MyMail @email.ne.jp and ID addresses @asahi-net.or.jp. Failed messages will be handled according to the sending domain's published policy and the recipient's filtering level. Its English announcement, dated 16 November, also schedules a separate change to its own domains' published DMARC policy for 8 December.
I would treat these as two preparation deadlines. Organizations sending into Asahi Net need to check authentication before November 26. Members sending with Asahi Net addresses through third-party systems need to check those routes before December 8. Custom-domain email is excluded.

Two deadlines affect different sides of delivery

The November rollout concerns what Asahi Net accepts as a receiving provider. It will evaluate incoming failures against policies that sending domains already publish.
The December rollout concerns messages using Asahi Net's shared domains in the visible From address. Asahi Net will publish a stronger policy for other receiving systems to consider when those messages fail DMARC.
Receiving: November 26
Default filtering begins for covered member addresses. The sender's policy and recipient's settings determine the announced handling.
Publishing: December 8
Asahi Net's shared domains move to p=quarantine. A later p=reject stage is planned, with no announced date.
Neither change creates a global receiver requirement or a new authentication standard. The practical effect depends on the direction of the message, its authentication results and the receiving system.

How November 26 filtering will handle failures

With DMARC filtering enabled, p=reject failures will be blocked and returned as errors at every spam-filter level, including none and weak. Selecting a low spam-filter level will not bypass that rejection rule.
Quarantine handling differs. The table summarizes Asahi Net's published delivery rules for messages that fail DMARC. These are DMARC-specific outcomes; other filtering decisions remain separate.

Sender policy

None or weak

Medium or higher

p=reject
Blocked; error returned
Blocked; error returned
p=quarantine
Inbox unchanged
Spam; [meiwaku] marker
p=none
Inbox unchanged
Inbox unchanged
Incoming DMARC failures from November 26, with DMARC filtering enabled.
For p=quarantine failures, medium or higher means the spam folder and a [meiwaku] subject marker. At none or weak, delivery remains unchanged to the inbox. A p=none failure also reaches the inbox unchanged at all levels under this policy.
Members will be able to switch DMARC filtering off in Web Mail after November 26. I would investigate the failed sending route first. Broadly disabling protection to accommodate one misconfigured sender removes the new safeguard for other incoming mail.

December 8 changes policy for Asahi Net addresses

The December change is intended to reduce impersonation of Asahi Net addresses. It covers the same shared domains. The Japanese original explicitly excludes custom-domain addresses from both changes.
December 8 starts the p=quarantine stage, not p=reject. A published policy requests treatment of authentication failures; receiving systems retain discretion over handling. Spam placement is not guaranteed at every recipient.
For a member using an Asahi Net address in an invoicing application or website, the important question is whether that application sends through a supported route. Entering an Asahi Net address in a From field does not give an unrelated server permission to authenticate for its domain.
Members cannot repair the shared domain's DNS themselves. Use the provider-documented sending settings and test the resulting messages. Where an application cannot support that route, discuss a supported sender identity with its administrator before changing production mail.

Check the authenticated domain in actual messages

DMARC passes when at least one authenticated SPF or DKIM path has the required domain relationship to the visible From address, known as alignment. Both mechanisms do not have to pass. An SPF pass for an unrelated return-path domain does not, by itself, satisfy DMARC.
I would inspect the final recipient's trusted Authentication-Results header for each sending route. This illustrative result shows an SPF failure with a passing DKIM signature for the From domain, which is enough for DMARC to pass:
Illustrative headers, not an Asahi Net delivery sampletext
From: Sender <sender@example.com> Authentication-Results: mx.example.net; spf=fail smtp.mailfrom=example.com; dkim=pass header.d=example.com; dmarc=pass header.from=example.com
Read the result added by the destination's own mail system, rather than trusting any authentication-looking header supplied by the sender. Preserve the complete message source when escalating a problem so an administrator can identify the receiving system's assessment.
A successful login to a sending application is not evidence that its outgoing mail passes DMARC. Likewise, a valid DNS record does not prove that every application signs correctly. The message received at the end of the route is the useful test.

Forwarding and message changes need separate tests

Forwarding changes the server connecting to the final receiver, which can cause SPF to fail. A surviving DKIM signature with the required domain relationship can still produce a DMARC pass. Forwarding is therefore a route to test, rather than proof that delivery will fail.
Mailing lists that modify signed content can break DKIM. Systems that replace attachments or rewrite the body need the same attention. SRS rewrites the envelope sender for forwarding, but does not guarantee SPF alignment with the original visible From domain.
Asahi Net's Japanese usage note specifically says automatic forwarding from its custom-domain email and manual forwarding are unaffected. That exception matters when deciding which routes need changes; the announcement does not say all forwarding will break.
Compare a direct delivery with the forwarded or mailing-list copy. If authentication changes, investigate the intervening system before changing the sender's DMARC policy or the recipient's protection settings.

What to check before the rollout dates

I would begin with actual mail routes, including low-volume systems that are easy to overlook. A password-reset service and a billing application can use different servers even when both display the same sender address.
For each route, send a representative message to a covered Asahi Net address and to a mailbox where full headers are available. Test direct delivery and any list or forwarding path used in production. Keep the results associated with the application that sent them.
Delivery before November 26 is not a sufficient acceptance test: the new filtering has not started. A currently delivered message still needs its authentication results checked. Record those results now, then check delivery again after the rollout. For December 8, repeat that exercise with messages using an Asahi Net shared-domain From address, since another provider's treatment of those failures is a separate part of the change.
  1. Route inventory. Record the visible From domain, sending system and return-path domain. Include website forms, scheduled jobs, newsletters and transactional messages.
  2. Authentication evidence. Check SPF, DKIM and the final DMARC result. Confirm the domain relationship rather than accepting an isolated SPF or DKIM pass.
  3. Indirect delivery. Compare list and forwarded copies with direct messages. Identify where signatures stop validating, especially after body or attachment changes.
  4. Provider settings. For Asahi Net addresses, follow its documented sending configuration. For domains you control, repair the responsible application or DNS configuration and retest.
For domains you control, Suped, our DMARC platform, provides DMARC monitoring to review reported sending sources and investigate authentication failures. Reports help identify routes absent from a small test batch; they complement message headers rather than replacing them.
A DMARC checker checks the published policy for a domain you manage. Use that alongside route tests. Neither a DNS lookup nor aggregate reporting guarantees inbox placement, and reporting depends on what receiving systems send.

Keep evidence ready for delivery problems

Before the deadlines, assign an owner to each sending application and save representative headers. For a later failure, collect the recipient address, sending time and returned error, then compare the affected route with a working one. For accepted but missing messages, check the spam folder and filtering level.
Ask the responsible administrator to correct the route and repeat the same test. Preserve protection while investigating, and avoid changing a domain-wide policy to accommodate a failure that belongs to one application.

Frequency asked questions

No. With filtering enabled, p=reject failures are rejected at all spam-filter levels. Quarantine failures go to spam only at medium or higher; none or weak leaves them in the inbox. A p=none failure also stays in the inbox under this DMARC policy.

No. December 8 starts p=quarantine for the covered shared domains. Asahi Net plans a later p=reject stage but has not announced its date. Other receiving systems retain discretion over how they handle failures.

No. One passing mechanism with the required domain relationship to the visible From address is sufficient for DMARC. Working DKIM is particularly useful when forwarding causes SPF to fail, provided the signature survives the route.

Custom-domain addresses are excluded from these announced changes. The Japanese original also identifies automatic forwarding from Asahi Net custom-domain email and manual forwarding as unaffected. Test other forwarding and mailing-list routes individually rather than assuming every route will fail.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing