Suped

How to set up DMARC/DKIM/SPF for Openwave

Published 22 Nov 2026
Updated 22 Nov 2026
10 min read
Summarize with
Openwave email authentication with DNS records and verification checks.
Set up Openwave email authentication by publishing your hosting provider's SPF authorization and DKIM public record, enabling DKIM signing for your domain, and adding a DMARC TXT record at _dmarc.yourdomain. DMARC passes when SPF or DKIM passes and its authenticated domain matches the visible From domain under your DMARC settings.
I start with the provider operating the Openwave service. Openwave deployments are provider-specific, so I do not assume a universal SPF include, DKIM selector or administration menu. I did not find a public Openwave authentication setup document with universal DNS values. Get the exact values for your service before editing DNS.

Add your domain

For a custom domain, have the provider provision it on the Openwave service and confirm ownership. If your domain already has working Openwave mailboxes, confirm the existing setup instead of creating it again.
  1. Confirm access. Sign in to your provider's account administration portal with domain-management access. If custom-domain provisioning is managed by support, request it through that provider.
  2. Register the domain. Supply the domain used in your visible From addresses, such as example.com. Ask the provider to confirm that it is enabled for outbound sending.
  3. Prove ownership. Publish the exact verification TXT or CNAME record if the provider requires one. Request a recheck and obtain confirmation that the domain is verified.
  4. Collect the records. Request the SPF authorization, Return-Path configuration and domain-specific DKIM records. Keep existing MX records unless you are also migrating incoming email.
Request these details from the Openwave service providertext
Sending domain: example.com Please provide the domain verification DNS record, if required. Provide the SPF include or outbound IP ranges for this service. Confirm the envelope sender / Return-Path domain. Provide the DKIM selector, signing domain and public DNS record. Confirm how to activate outbound DKIM signing for this domain.
If you send using an address on a provider-owned domain, the provider controls its DNS authentication. Ask it to correct SPF or DKIM failures. Publish records only for domains you control.

Set up SPF

SPF checks the SMTP envelope sender domain, normally visible in the delivered message's Return-Path. I inspect that domain before choosing where to publish SPF.
  1. Identify the domain. Send a message through Openwave and inspect Return-Path in the received headers. If it uses bounce.example.com, check SPF there; an apex SPF record is not inherited by subdomains.
  2. Authorize the service. Add the provider-issued include mechanism or IP ranges to the SPF TXT record at the required name. Do not guess include:openwave.ai or copy the vendor's corporate SPF record.
  3. Merge existing senders. Maintain one v=spf1 record at each relevant name. Insert the new authorization before the final all mechanism, preserving existing legitimate senders and the current all qualifier.
  4. Check the limit. Keep evaluation within SPF's 10 DNS-lookup-causing terms, including nested includes. Ask the provider to simplify its authorization if the combined policy exceeds the limit.
Inspect SPF at the actual envelope sender domainbash
dig +short TXT example.com dig +short TXT bounce.example.com
Replace the example domains above with the Return-Path domain observed in your test. Openwave supports Return-Path alignment, but the provider must configure your deployment to use your domain or an appropriate subdomain.
Run the SPF check against that actual domain after publishing. It checks the DNS policy; a live email test is still needed to confirm that Openwave uses an authorized outbound IP.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
If the provider delegates a bounce name through CNAME, publish its supplied CNAME rather than adding a conflicting TXT record at the same name. Follow the provider's record type and target exactly.
A Return-Path under an unrelated provider domain does not give your From domain SPF alignment. If the provider cannot enable a custom Return-Path for your account, adding SPF at your apex will not fix that mismatch. Use passing DKIM with the correct signing domain for DMARC.

Set up DKIM

DKIM needs both a published public record and an active signer on the outbound service. I verify the signing domain in an actual message rather than treating a DNS check as proof of signing.
  1. Obtain the selector. Request the selector and signing domain from the provider. The DNS name is selector._domainkey followed by that signing domain; do not assume a default selector.
  2. Publish the record. Create the supplied TXT public-key record or CNAME delegation. Copy the complete value. Keep private signing keys on the mail service, never in public DNS.
  3. Activate signing. Ask the provider to enable outbound DKIM signing for your domain after DNS resolves. Request a 2048-bit RSA key where supported.
  4. Verify a message. Send through every outbound route you use. Confirm dkim=pass and inspect the DKIM-Signature d= value for your From domain or a matching subdomain under relaxed DMARC settings.
Query the provider-issued DKIM selectorbash
dig +short TXT selector._domainkey.example.com dig +short CNAME selector._domainkey.example.com
Replace selector and example.com with the values provided for your domain. If your DNS editor appends the zone automatically, enter only the relative name so the domain is not added twice.
A valid signature needs the right domain
A dkim=pass result signed only with an unrelated provider domain does not satisfy DMARC for your From domain. Have the provider enable your domain as the signing domain. During rotation, keep the old selector published until messages signed with it have cleared delivery queues.

Set up DMARC

Publish DMARC in your own DNS after configuring the Openwave sending path. For a domain without an enforcement policy, I start with p=none and aggregate reporting.
  1. Inspect the policy. Look up TXT at _dmarc.example.com. If the existing record uses p=quarantine or p=reject, retain that policy while adding Openwave authorization and fixing signing.
  2. Create one record. For an initial monitoring setup, add one TXT record with the host _dmarc and the value shown below. Replace the example reporting address with a mailbox or reporting destination you control.
  3. Keep relaxed matching. The default SPF and DKIM alignment mode is relaxed. A subdomain such as bounce.example.com can match example.com. Preserve stricter settings if already required, and configure exact domain matches.
  4. Confirm reporting. Ensure the reporting mailbox accepts aggregate report attachments. For a reporting destination outside your domain, complete the destination's external-report authorization requirements.
Initial monitoring record at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use the DMARC record generator to build the record with your real reporting address. Edit the existing DMARC record when one is present; publishing another policy at the same name causes validation problems.
Check the domain used in the visible From address below. The checker confirms policy discovery and DNS configuration; it does not prove that a message is signed correctly.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
A p=none policy requests no DMARC enforcement against failing messages. It lets you collect evidence before changing policy, but receiving systems still apply their own spam and security rules.
Expect aggregate reports after receivers process their reporting intervals, commonly within 24-48 hours of sending. Check the reporting address and external authorization if reports do not arrive.

Verify and troubleshoot

I test the complete sending route after DNS changes, including webmail and any configured SMTP application. Send directly to the test address so forwarding does not change the initial result.
  1. Send a fresh test. Use the email tester below to obtain a destination, then send a message from your Openwave-hosted mailbox. Use the same From address and sending route as production mail.
  2. Read trusted results. Inspect the receiving system's Authentication-Results and the tester diagnosis. Target spf=pass, dkim=pass and dmarc=pass, with the expected authenticated domains.
  3. Isolate the failure. For SPF errors, check the envelope domain and actual outbound IP. For DKIM errors, compare the selector and signing domain with DNS, then ask the provider to inspect signing.
  4. Retest after changes. Wait for the previous DNS TTL and cached negative answers to expire, then send another message. Check aliases and application SMTP routes separately.
The email tester prompts you to send a test message and returns a diagnosis of authentication and other delivery checks. It is the quickest check of the actual message, including whether the provider enabled DKIM signing.
Use a harmless test body with the subject Openwave authentication test. Keep the full headers and sending time if you need the provider to investigate an unexpected outbound route.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
A DMARC pass requires one passing authentication method whose domain matches the From domain under your policy. Both SPF and DKIM passing gives useful redundancy, especially because forwarding commonly breaks SPF.
If SPF alignment fails while DKIM passes with a matching domain, DMARC still passes. If both methods fail DMARC's domain-matching requirement, a raw SPF or DKIM pass on its own does not help.

Observed result

Likely cause

Next action

SPF permerror
Duplicate or over limit
Merge or simplify
SPF mismatch
Provider Return-Path
Configure custom domain
DKIM missing
Signing inactive
Enable domain signing
DKIM key missing
Selector DNS absent
Publish exact record
DKIM mismatch
Provider signing domain
Enable custom signing
DNS checks pass
Sending path differs
Send a live test
Use the received message to distinguish DNS problems from sending configuration.
The following headers are an illustrative successful result, not a required Openwave selector or Return-Path format. Replace the example values with the domains observed in your received message.
Illustrative authentication resultstext
From: sender@example.com Return-Path: <bounce@bounce.example.com> Authentication-Results: receiver.example; spf=pass smtp.mailfrom=bounce.example.com; dkim=pass header.d=example.com header.s=selector; dmarc=pass header.from=example.com

Get alerted when it breaks

Suped is our DMARC platform for ongoing authentication monitoring. It turns aggregate reports into source-level results and detected issues, so you can spot an Openwave signing change or a new unauthorized sending source.
  1. Enable issue alerts. In Suped notification settings, enable Issues detected and Sending sources need verification. Add DMARC summaries for regular review.
  2. Verify the source. Review the source table and confirm that the Openwave traffic belongs to your provider before marking it verified. Compare sending IPs with provider confirmation and your own test messages.
  3. Investigate the record. Open a failing record in Detail view to inspect SPF, DKIM, DMARC and rDNS. Compare DNS history with the time the failures started.
  4. Close with evidence. Apply the detected issue's fix steps, send another live test and confirm that later reports show the expected result. Keep the provider ticket open until its affected outbound routes are covered.
Our DMARC monitoring workflow keeps the sending-source inventory and authentication diagnostics together. I review legitimate source failures separately from unauthorized traffic before deciding whether a policy change is safe.
Alerts depend on incoming evidence
DMARC aggregate reports arrive after the receiver's reporting interval. Suped alerts on detected issues as the relevant evidence becomes available; this is not a live feed of every Openwave message. Use a fresh email test to verify an urgent fix.

Secure your domain with p=reject

Move to p=reject after every legitimate sending service passes DMARC consistently. I use source-level evidence, including infrequent business mail, rather than a single successful Openwave test.
  1. Inventory every sender. Review Suped's verified and unverified sources. Account for application mail and other services using the same From domain, then fix each legitimate source's DMARC failures.
  2. Observe normal activity. Monitor through a complete business sending cycle, including infrequent jobs. Confirm Openwave DKIM stays valid across the outbound routes and selectors in use.
  3. Stage enforcement. If starting at p=none, move to p=quarantine, review subsequent reports and delivery problems, then move to p=reject. Preserve an existing stronger policy while fixing newly added senders.
  4. Keep reporting active. Retain the real rua destination during each change. Review subdomain policies and forwarding behavior, then keep alerts enabled after enforcement.
Suped's Hosted DMARC lets you manage policy through our dashboard after its DNS delegation is configured. Use its policy controls alongside source verification and issue diagnostics to decide when to enforce rejection.
Ready to enforce
Each legitimate source is identified and passes DMARC. Openwave tests show the expected signing domain, and normal business traffic is covered.
Keep the real report destination, apply the next policy stage and check new reports for legitimate failures.
Resolve before enforcing
Legitimate sources are still unidentified, Openwave signs with an unrelated domain, or an application bypasses the configured sending route.
Assign each failure to its service owner and verify the fix. If already enforcing, repair that sender without weakening the domain's policy.
This example changes only the enforcement policy. Replace the reporting address with your working destination before publishing it as your single DMARC policy record.
Enforcement record after legitimate senders are verifiedtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
A reject policy requests rejection of messages that fail DMARC. Receivers retain their own handling decisions, and authentication does not guarantee inbox delivery.

Frequency asked questions

Use the include or outbound IP ranges supplied by the provider operating your Openwave service. I did not verify a universal Openwave include. Do not invent include:openwave.ai or copy the SPF policy used for Openwave's own corporate email.

Get it from your provider's domain-authentication configuration or support team. For a signed message, the s= tag in DKIM-Signature identifies the selector and d= identifies the signing domain. Query selector._domainkey followed by that signing domain.

A hostname ending in cloud.openwave.ai points to Openwave-branded infrastructure. The provider operating the service can confirm which deployment and outbound IP pool it belongs to. I treat the suffix as an attribution clue: verify the actual source IP, SPF result and DKIM signing domain before authorizing a source. The suffix does not prove that a message is legitimate.

Yes. DMARC passes when DKIM passes and the signing domain matches the visible From domain under the policy, even if SPF does not match. If your account cannot use a custom Return-Path, expect that SPF mismatch and make correct DKIM signing a requirement.

Keep an existing p=reject or p=quarantine policy. Configure the new sending path and verify a test before production use. The p=none example is for an initial monitoring setup on a domain that is not already enforcing DMARC.

DNS checks show that records resolve. The message still needs an authorized outbound IP or a valid DKIM signature with a domain that matches the visible From domain under DMARC. Check the actual sending route, Return-Path and DKIM-Signature in a fresh received message.
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