Source review dated 8 November 2026. Provider settings and acceptance exercises below are documentary guidance, not executed account, DNS or message tests.
Confirm the RightNow deployment before choosing a procedure
The catalogue topic names Oracle RightNow. This article documents a narrower, verified public procedure: Oracle B2C Service OCI Mail through Configuration Assistant. It is not evidence that every legacy RightNow mailbox uses that route. Record the actual service name, environment, interface, mailbox and sending workflow. Obtain tenant confirmation that Configuration Assistant e-Domains applies before using the steps below. The original broad configuration scope remains on hold until the legacy or current route is established.
Oracle's public e-Domains overview says the feature manages email domains, DKIM configuration and approved senders. That establishes the administration surface, not the status of a particular customer domain. Neither an Oracle subscription nor an old RightNow hostname proves this workflow is enabled. Oracle B2C Service OCI Mail e-Domains
Separate incident replies, automated notifications and outreach messages in the inventory. Use a distinct test case for each route that the organization depends on. Preserve the existing working provider address until the custom-domain route has been approved. A reply address is not necessarily the envelope sender or DKIM signing identity.
Obtain the DKIM record through Configuration Assistant
For a tenant confirmed to use this route, Oracle documents the following sequence: open e-Domains in Configuration Assistant, choose Add DKIM under Configure DKIM, select the domain, enter a unique selector and submit. After the successful-addition message, expand the domain under Available Domains and copy the generated record for the DNS administrator. The documentation notes that activation can take a few hours after publication. Oracle B2C Service Add DKIM for a Domain
The selector is a name used to find a key, not a secret password. Do not invent a selector target based on another customer's configuration. Keep the returned record type, owner and value together with the selected domain and environment. Before creation, establish who owns any existing selectors and whether a rotation is already underway. The article supplies no production-ready record because none was issued by a live tenant.
If the expected e-Domains controls are unavailable, stop this branch. Ask the product administrator or Oracle support to identify the deployment and applicable mailbox procedure. Do not improvise a raw OCI Email Delivery change against an unrelated tenancy simply because the service uses Oracle infrastructure.
Publish without disturbing inbound mail or existing signatures
Send the issued public record to the administrator of the authoritative DNS zone. Record the full owner and the DNS editor's relative-name behavior so the domain is not appended twice. Preserve the old answer before an authorized edit. If the requested owner conflicts with an existing record, investigate the ownership conflict before deletion.
Read the published answer from the authoritative service, then check a recursive resolver after the relevant cache lifetime. DNS publication and sender activation are separate events. A successful submission in Configuration Assistant does not show that the public key is visible. A public key does not show that the outbound application is signing. DKIM verification depends on the received signature's d= domain and s= selector. DKIM RFC 6376
This outbound authentication change does not authorize replacing MX records, moving nameservers, or altering inbound support-ticket routing. If a separate mail-routing change is required, plan it with its own acceptance and recovery criteria.
Treat SPF and sender approval as separate evidence gaps
The public e-Domains overview includes approved-sender management, but this research did not establish the applicable sender approval state or tenant-specific SPF prescription. Obtain the exact requirements for the confirmed deployment. Do not borrow an OCI region include, a Fusion SPF value or a historical RightNow example without provider confirmation for this route. Oracle B2C Service OCI Mail e-Domains
Where a policy change is needed, evaluate the actual SMTP envelope identity. Maintain one SPF policy for a given owner and retain all authorized senders. SPF pass at a provider-owned return domain can be valid without aligning to the customer From domain. DMARC requires alignment through a passing SPF or DKIM result; publishing both record types is not itself a DMARC pass. SPF RFC 7208 DMARC RFC 9989
Earlier documentary research recorded a support-portal redirect without readable legacy mailbox instructions. That historical access result was not rerun in this review, and the unavailable material is not treated as reviewed setup evidence. This limitation is why the original RightNow configuration claim remains explicitly unresolved.
Verify a real support workflow at the receiver
After DNS and activation are confirmed, send a harmless representative incident response to an approved external test mailbox. Capture the full headers before a forwarding system changes the message. Record the visible From, envelope identity, DKIM signing domain and selector, and trusted receiver authentication results. Compare the domains under the policy's configured alignment mode.
Repeat for other workflows in the inventory. A successful manually composed response does not establish authentication for a separate notification or outreach path. If a message is not sent at all, inspect application and queue evidence before diagnosing DNS. If DKIM fails only after a gateway modifies the message, compare a direct-receiver test with the routed test instead of rotating keys prematurely.
B2C Service route worksheet
This is an unfilled implementation worksheet, not a claim of successful configuration.
- Product branch: legacy RightNow or confirmed B2C Service OCI Mail; tenant, interface and supporting administrator evidence.
- Workflow coverage: incident reply, notification or outreach; originating mailbox and business owner.
- DKIM issuance: chosen domain, selector, generated record, creation response and record owner.
- DNS evidence: authoritative zone, previous value, published answer, observation time and activation status.
- Unresolved controls: approved-sender requirement, SPF identity and prescription, legacy-route documentation and support reference.
- Receiver evidence: message identifier, From domain, envelope domain, d=, s=, result and alignment decision for every workflow.
- Recovery: last known working sender configuration, trigger for rollback, support contact and sign-off owner.
Fictional diagnosis of a selector on the wrong tenant
This example is fictional. A support team labels its service RightNow and publishes a selector generated in a separate OCI account. The incident reply remains unsigned. The initial hypothesis is DNS propagation, but a comparison of the application tenant and record-issuance tenant shows they are not the same route.
The team freezes further DNS changes, identifies whether its B2C Service deployment uses Configuration Assistant e-Domains, and requests a record from the correct administration surface. A new controlled incident reply then becomes the acceptance test. Until its headers show aligned authentication, the incident is unresolved. The example does not establish that a legacy deployment can be repaired with e-Domains.
Preserve the open approval gates
No customer tenant, live DNS or received message was tested. Broad RightNow coverage, deployment-specific SPF, sender approval, visual inspection and human SME review remain pending. This narrower article can support documentary review but must not be counted as a completed implementation of the original provider scope.