Suped

How to set up DMARC/DKIM/SPF for Optus

Published 21 Nov 2026
Updated 21 Nov 2026
11 min read
Summarize with
Optus email authentication with SPF, DKIM and DMARC.
Optus manages SPF, DKIM and DMARC for addresses ending in @optusnet.com.au. Customers cannot edit that shared domain's DNS records. Use authenticated Optus SMTP, then test a delivered message. For an address on a domain you own, publish authentication records at its DNS host using the instructions for your actual sending service.
I check the domain in the visible From address first. Ordinary OptusNet mailboxes have no custom-domain onboarding step. If you send with your own domain through an Optus service, confirm that service supports the domain and obtain its approved SPF and DKIM settings before changing DNS.

Set up SPF

For an OptusNet mailbox, the practical first step is SMTP authentication. This logs your email application into the sending server. SPF is a separate check that the receiving server performs against the envelope sender domain.
  1. Confirm access. Sign into Optus Webmail with your existing mailbox credentials. Use the OptusNet address as your From address when testing that mailbox.
  2. Configure sending. Set your application's outgoing server to mail.optusnet.com.au. Use port 587 with STARTTLS, or port 465 with SSL/TLS. Enable password authentication and enter your full OptusNet email address and mailbox password.
  3. Check the Return-Path. Send a message to an external mailbox and inspect the received Return-Path and SPF result. For your own domain, confirm that the envelope sender uses that domain or a qualifying subdomain.
  4. Update owned DNS only. If your Optus service supports your custom domain, obtain its approved SPF include or outbound IP ranges. Merge those mechanisms into one SPF TXT record at the envelope sender domain. Preserve other authorized senders.
Optus's support article "Using an email application with OptusNet email" documents the encrypted SMTP settings above. Changing an application's display name or Reply-To address does not change the domain checked by SPF.
I do not copy Optus's entire SPF record into a customer domain or assume an include value. An Optus internet connection alone is not a reason to authorize Optus mail servers. Check the service that actually sends the message.

SPF checker

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

?/16tests passed
Enter the envelope sender domain in the SPF checker. For a shared OptusNet mailbox, that lookup is diagnostic; Optus controls any repair to its SPF record. For a domain you control, correct duplicate SPF records and keep evaluation within the 10 DNS-lookup limit.
If the sending service cannot use your domain in the Return-Path, adding SPF to your visible From domain will not fix SPF alignment. In that case, no SPF addition for that service is needed at your From domain. DMARC can still pass through a valid DKIM signature with domain alignment.

Set up DKIM

DKIM signing happens on the sending server. Publishing a public key without configuring the matching private key on that server does not enable signing. OptusNet customers cannot create selectors under a domain owned by Optus.
  1. Inspect a message. Open the full headers of a newly delivered test message. Find DKIM-Signature and record its d= signing domain and s= selector, if present.
  2. Check verification. Read the recipient's trusted Authentication-Results header. Look for dkim=pass, then compare the signing domain with the visible From domain under the domain's DMARC alignment settings.
  3. Request service details. For a custom domain, ask Optus whether your specific service supports signing with that domain. Request its exact selector, DNS record type, and public value or CNAME target. There is no universal selector to guess.
  4. Publish and retest. If supported, add the supplied record at selector._domainkey.your-domain, using the actual selector and domain. Complete any provider activation step, wait for DNS caches to expire, and send another message.
I use the selector found in a real message rather than trying common selector names. If an OptusNet message has no signature, report that evidence to Optus; a DNS record on an unrelated domain cannot add a signature to their outgoing mail.
A DKIM pass alone is insufficient for DMARC when the signing domain does not match the From domain under the applicable alignment rules. Either SPF or DKIM must supply a passing result with domain alignment.
SPF route to a DMARC pass
The sending IP passes SPF for the envelope sender domain. That domain matches the visible From domain under the configured alignment mode.
Forwarding often changes the sending IP, so SPF alone is a fragile basis for forwarded mail.
DKIM route to a DMARC pass
A signature verifies, and its d= domain matches the visible From domain under the configured alignment mode.
This route can preserve DMARC authentication through forwarding when the signed content remains intact.
If your service provides neither a matching Return-Path nor a matching DKIM signature, it cannot produce a DMARC pass for your custom From domain. Change the sending configuration or use a sending service that supports your domain before enforcing rejection.
For an ordinary OptusNet mailbox, keep using the assigned address and escalate provider-side signing failures to Optus. There is no customer DKIM switch documented in the public OptusNet mailbox setup instructions.

Set up DMARC

Publish DMARC only for a domain you control. An individual @optusnet.com.au mailbox inherits Optus's domain policy; customers cannot set a separate policy for their mailbox.
  1. Read the existing policy. Query the TXT record at _dmarc followed by your From domain. Save its current value. If the domain already uses p=quarantine or p=reject, keep that policy while fixing authentication.
  2. Create a monitoring record. For a domain without enforcement, start with p=none and a working aggregate-report destination. Publish one DMARC TXT record at _dmarc, not a second record beside an existing policy.
  3. Set the reporting address. Replace the example mailbox below with the address that will receive and process your reports. For an external reporting domain, complete any required reporting authorization.
  4. Verify publication. Check the saved DNS name, record syntax, and reporting destination. A DNS editor that appends your domain usually needs only _dmarc in its Host field.
Monitoring template: TXT at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace example.com and the report address with your own values. The example mailbox does not collect reports for you. A p=none policy requests monitoring without requesting quarantine or rejection for DMARC failures.
Use our DMARC record generator to build the record. If a stronger policy is already present, retain it and its existing reporting destinations rather than replacing it with this monitoring template.

DMARC checker

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

?/7tests passed
Enter your From domain to confirm that the published DMARC record is discoverable and valid. Checking optusnet.com.au shows the provider's configuration; it does not grant control over that domain.
A valid DNS record does not prove that actual mail passes DMARC. I verify both the published policy and the authentication result on a newly sent message before considering setup complete.

Verify and troubleshoot

Test the actual sending path. A message sent through Webmail and one sent through a desktop application can expose different submission problems, even when they use the same address.
  1. Send a baseline. Use Optus Webmail to send a test to your own mailbox, as Optus's troubleshooting instructions recommend. Then send externally to inspect authentication at the receiving system.
  2. Test the application. Repeat through your normal email application using the same From address. If Webmail works but the application cannot send, recheck its SMTP server, encryption, and saved credentials.
  3. Read recipient results. Inspect the receiving system's trusted Authentication-Results header for spf=, dkim=, and dmarc=. Compare the authenticated domains with the visible From domain.
  4. Separate failure types. For login or daily-limit errors, check SMTP authentication first. For SPF or DKIM failures on the shared Optus domain, send Optus the full message headers and bounce text through its support channel.
Our email tester is the quickest way to check a real message. It supplies a destination address; send a fresh email there through the Optus route you are configuring, then review the diagnosis.
A lookup checks DNS. A message test also checks whether the server actually uses the expected envelope sender and DKIM signature. Keep the tester's generated recipient unchanged so it can associate the message with your test.

Email tester

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

?/43tests passed
Check DMARC first, then inspect the underlying SPF and DKIM results. If SPF alignment fails but a valid DKIM signature has domain alignment, DMARC still passes. If both authentication paths lack domain alignment, DMARC fails even when each reports a separate pass.
Use the recipient's results as evidence. A header inserted earlier in transit is not automatically trustworthy, and an SPF softfail is not an SPF pass.

Result

Next check

SMTP login fails
Credentials and TLS
SPF fails
Envelope sender and IP
DKIM fails
Selector and signature
DMARC fails
From-domain alignment
DMARC passes
Other delivery errors
Common results and the next check
When testing Webmail, confirm the sender is the intended OptusNet mailbox. Do not change the From address to a custom domain unless the sending service has been configured to authenticate that domain.
Optus's "Can't send or receive email: OptusNet troubleshooting" article uses Webmail testing to distinguish mailbox problems from application configuration problems. The login illustration below identifies the product used for that check.
Illustrated Optus Webmail login for testing an existing OptusNet mailbox.
Illustrated Optus Webmail login for testing an existing OptusNet mailbox.
An inbox placement problem after DMARC passes needs separate investigation. Keep the recipient's rejection code and message identifier; changing a working authentication record does not resolve every delivery error.

Get alerted when it breaks

For a domain you control, Suped is our DMARC platform for monitoring authentication after setup. Its reports identify sending sources and failures, while issue notifications connect detected problems with steps to fix them.
  1. Route reports. Set rua to your assigned Suped reporting destination while retaining your existing DMARC policy. Check that aggregate reports arrive before relying on report-based notifications.
  2. Verify sources. Review the sending-source table and mark legitimate sources as verified after confirming ownership. Investigate unfamiliar sources rather than adding every reported IP to SPF.
  3. Enable notifications. In Suped notification settings, enable Issues detected and Sending sources need verification. Configure DMARC summary emails for routine review.
  4. Resolve and retest. Open a detected issue, follow its Steps to fix, and verify the change. Send another email test and review subsequent aggregate reports to confirm the repair.
Our DMARC monitoring brings source-level authentication results and issue investigation into one workflow. I review changes by legitimate source because a combined domain pass rate can hide a small but important failing sender.
Aggregate reporting follows the receiving provider's reporting schedule. Treat these notifications as report-based detection rather than a live alert for every individual SMTP transaction.
Shared domains need provider action
An OptusNet customer cannot redirect optusnet.com.au DMARC reports to a personal monitoring account. Suped cannot change Optus-owned DNS. For that shared domain, keep test results and escalate authentication failures to Optus.
Use continuous domain reporting for domains you administer. Use individual message tests and provider support for a shared OptusNet mailbox.

Secure your domain with p=reject

Move a domain you control to p=reject after its legitimate sending paths pass DMARC reliably. I base that decision on source-level evidence, including infrequent business mail, rather than a fixed waiting period.
  1. Inventory real senders. Use Suped reports to identify every legitimate source using your domain. Test business systems that send only occasionally, including billing applications and scheduled notifications.
  2. Fix authentication. Resolve failures for each authorized source. Confirm a passing SPF result with domain alignment or a passing DKIM signature with domain alignment. Review forwarding paths before tightening policy.
  3. Stage enforcement. After clean monitoring, use p=quarantine and inspect legitimate delivery before switching to p=reject. If already enforcing, retain that protection while fixing specific sources. Review subdomain policies before changing the parent policy.
  4. Keep evidence and alerts. Retain the prior DNS value, keep aggregate reporting enabled, and check Suped issues after each policy change. Re-test the Optus sending path whenever its configuration changes.
Suped's Hosted DMARC lets a domain administrator manage policy in our dashboard after its DNS delegation is configured. This makes policy staging practical while keeping authentication reports available for the next decision.
I do not rely on percentage sampling as a safety control. Stage changes through monitored policy transitions and explicitly scoped domains. Resolve legitimate failures before requesting rejection.
Enforcement template: TXT at _dmarc.example.comtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Replace the example reporting address with your working destination and preserve any other intentional policy tags. This policy requests rejection of DMARC-failing mail; receiving systems still apply their local handling rules. Only Optus can make this change for optusnet.com.au.
Recheck legitimate sources after enforcement, especially after a sending-server change. If one source starts failing, use its authentication results to repair the cause rather than weakening protection across the whole domain.

Frequency asked questions

No. DMARC is a domain policy, and Optus controls optusnet.com.au. Configure authenticated sending for your mailbox, test a message, and report provider-side authentication failures to Optus. Publish your own policy only for a domain you control.

There is no universal customer SPF include specified in the public OptusNet mailbox setup instructions. For a custom-domain service, obtain the approved include or outbound IP ranges for that service. Standard OptusNet mailbox users do not publish an SPF record themselves.

Read the s= value in DKIM-Signature on a newly delivered message and pair it with the d= signing domain. Selectors are service-specific. If the message has no DKIM signature, guessing a selector or generating a key locally will not enable Optus server-side signing.

SPF can pass for a Return-Path domain that does not match the visible From domain under DMARC alignment rules. DMARC then needs a passing DKIM signature with domain alignment. Adding SPF to the From domain does not change an envelope sender controlled by the sending service.

That suffix suggests an Optus-managed host, but rDNS alone does not establish which application or mailbox sent a message. An Optus network connection is not proof of authorized OptusNet email. Check the connecting IP, trusted Received headers, and SPF or DKIM results before approving the source.

SMTP authentication logs your application into the outgoing server. It does not edit DNS, create a DKIM signature, or guarantee a DMARC pass. Optus requires authenticated settings for normal mailbox sending; verify the receiving server's authentication results after configuring them.
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