[ Sending-service guides ]

Verify Fusion Applications notification authentication per environment

Use the Fusion-specific support process, confirm release applicability and test each environment’s actual notification identity.

By the EmailAuth research team · 5 min read

[ Key points ]

  • Use the pinned Fusion-specific per-environment support process.
  • Confirm current release, infrastructure and From-address scope.
  • Keep DNS publication, support activation and message evidence separate.
On this page
  1. Key points
  2. Takeaway
  3. By role
  4. Frequently asked questions
  5. Sources
  6. Glossary
  7. Related guides

[ Takeaway ]

Keep DNS publication, support activation and message evidence separate.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Validate the actual route

Apply the documented release guidance only after validating the actual environment.

Next steps

  1. Record the product, environment and sending identity.
  2. Verify public DNS and a fresh receiver message.
  3. Retain exact settings and a rollback decision.

CISO / SecOps

Approve evidence rather than branding

A support completion flag cannot replace receiver-side alignment evidence.

Next steps

  1. Review authentication and alignment separately.
  2. Limit access and redact message content in evidence.
  3. Keep human SME approval and publication pending.

Founder / Non-technical

Protect the business workflow

Production and test notifications require separate acceptance.

Next steps

  1. Name the business owner and critical messages.
  2. Approve a controlled pilot before expanding traffic.
  3. Keep a usable recovery route and escalation contact.

[ FAQs ]

Frequently asked questions

Can I configure Fusion through the OCI DKIM console?

Not using the general Email Delivery procedure. Use the confirmed Fusion-specific process.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Which release supports this article?

The detailed public reference is the Applications Common 25D guide. Validate current tenant applicability before implementation.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Is one request enough for every environment?

The cited procedure is per environment. Keep separate activation evidence for each.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Does the HCM single-address rule apply to all Fusion products?

No. Preserve its documented HCM scope and confirm other products separately.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Should I reuse an old selector?

Use the record issued for the actual environment and resolve possible selector conflicts through the supported workflow.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Can I create a second SPF record for Fusion?

No. Review the existing policy and integrate authorized changes without competing SPF policies.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Does an Oracle support closure prove DMARC?

No. Inspect a new received notification and verify the aligned authentication path.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

Is all Oracle Fusion coverage complete?

No. This candidate is limited to the stated notification route, with broader product scope and live acceptance still held.

Fusion Applications configure email security Oracle HCM DKIM and DMARC support OCI Email Delivery configuring DKIM RFC 7208 Sender Policy Framework RFC 6376 DomainKeys Identified Mail RFC 9989 Domain-based Message Authentication Reporting and Conformance

[ Sources ]

Sources

  1. Fusion Applications configure email security

    Sections §25D prerequisite10–11; SPF18–20; per-environment38; SR40–61; From62

  2. Oracle HCM DKIM and DMARC support

    Sections HCM7–10: SR, OCI prerequisite, single From

  3. OCI Email Delivery configuring DKIM

    Sections Excluded Fusion/Classic services13–18; distinct selectors

  4. RFC 7208 Sender Policy Framework

    Sections §3.2; 3.3; 4.6.4

  5. RFC 6376 DomainKeys Identified Mail

    Sections §3.5; 3.6.2; 6.1

  6. RFC 9989 Domain-based Message Authentication Reporting and Conformance

    Sections §4.4; 4.7; 4.10; 5; Appendix A.6 removal of pct

[ Glossary ]

Glossary

Visible From
The author address shown in the message From header.
Envelope sender
The SMTP sender identity normally represented by Return-Path after delivery.
DKIM selector
The s= value used with the signing domain to locate a public key in DNS.
Alignment
The relationship between an authenticated domain and the visible From domain required by DMARC.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base