How to set up DMARC/DKIM/SPF for Maxo
Published 22 Nov 2026
Updated 22 Nov 2026
11 min read
Summarize with

Set up Maxo email authentication by authorizing its confirmed outbound servers in SPF, enabling DKIM signing for your domain where your Maxo service supports it, and publishing a DMARC TXT record at _dmarc.yourdomain. Configure Maxo's supported custom return path so SPF authentication uses your domain, then test a message sent through the actual Maxo service.
I start with the account-specific DNS values. Maxo's public support material does not establish a universal customer SPF include, DKIM selector or custom-domain activation procedure. Get those details confirmed by Maxo support before changing DNS. A new DMARC deployment starts with p=none; retain p=quarantine or p=reject if either is already in place.
Add your domain
For a customer-owned sending domain, have Maxo confirm provisioning and ownership verification. Its public website is branded MaxoTel; the documented portal workflows focus on telecommunications services, so a custom-domain email setup needs confirmation for your specific service.
- Confirm the sender. Inspect the visible From address on a real message. Apply these DNS changes to a domain you control. If the From address belongs to Maxo, its domain administrator controls that authentication.
- Request provisioning. Contact Maxo support through its Support Centre. Give your account identifier, sending domain and the service producing the email. Ask whether customer-domain DKIM signing is available for that service.
- Collect DNS values. Request the approved SPF authorization, custom return-path hostname and any required verification record. Request the DKIM selector and public TXT value or CNAME target if signing is supported.
- Verify ownership. Publish only the verification record Maxo requests, at your authoritative DNS provider. Ask support to confirm the domain is active and the custom return path is configured before testing.
I keep the support response with the DNS change record. It should identify the exact domain and sending service covered by each value.
Open the MaxoTel website, choose Support, then Contact us to reach the Support Centre. Use the support enquiry option to request these details.

Illustrative reconstruction of MaxoTel's Support Centre and support enquiry option.
Address verification for MaxoTel email-to-fax is a separate workflow. Its Virtual Fax guide describes adding an email address and confirming a verification email; that does not establish DKIM signing for mail sent using your domain.
Leave inbound MX routing intact while configuring outbound authentication. Change MX records only when Maxo explicitly requires an inbound mail migration.
Set up SPF
Publish SPF at the domain used by the SMTP envelope sender, normally visible in the delivered Return-Path. With relaxed DMARC alignment, a return path such as bounce.example.com matches a visible From domain of example.com.
- Inspect existing DNS. Find the TXT record beginning v=spf1 at the actual envelope-sender domain. A subdomain does not inherit the SPF record at the root domain.
- Authorize Maxo. Merge the exact Maxo-approved include or outbound IP mechanisms into the existing SPF record, before its final all mechanism. Keep the other authorized senders and publish one SPF record per hostname.
- Configure the return path. Have Maxo apply the custom return-path domain to your sending service. Adding an SPF record does not change the envelope sender by itself.
- Check lookup limits. Keep SPF evaluation within 10 DNS-triggering terms, including nested includes. Resolve duplicate records or permerror results before sending production mail.
Do not infer an SPF include from maxo.com.au or copy Maxo's corporate SPF record. Neither establishes the approved outbound servers for your customer service.
Enter the envelope-sender domain in the SPF checker below. If Maxo uses a dedicated bounce subdomain, check that hostname as well as any root-domain SPF record used by your other mail.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
A valid SPF record confirms DNS syntax and authorization structure. A delivered message confirms which envelope domain and outbound IP Maxo actually used.
If the message still uses a provider-owned return path, editing your root SPF does not fix SPF alignment. Ask Maxo to activate the custom return path. DMARC still passes when DKIM passes with a matching domain, even while SPF alignment fails.
Inspect SPF records, replacing the example hostnamesbash
dig +short TXT example.com dig +short TXT bounce.example.com
Set up DKIM
DKIM needs both a public DNS record and signing on Maxo's outbound server. I confirm signing support first; a DNS key alone cannot make Maxo sign a message.
- Obtain the selector. Ask Maxo for the selector and signing domain assigned to your service. Do not assume the selector is default, mail or selector1.
- Publish the record. At the hostname supplied by Maxo, add its public TXT key or CNAME target exactly. Check whether your DNS editor automatically appends the domain name.
- Activate signing. Have Maxo enable DKIM using your domain and the matching private key. Keep private keys out of public DNS and support attachments.
- Verify a new message. Confirm the receiving server reports dkim=pass and that the signature domain matches the visible From domain under your DMARC alignment mode. A passing signature for Maxo's own domain is insufficient for your domain.
If your service has no customer-domain DKIM option, ask Maxo for a supported authenticated sending route. Record that limitation before considering p=reject.
The two checks below prevent a common mistake: treating a published selector as proof that outbound messages are signed.
Public DNS
The selector hostname resolves to the public key or the CNAME target supplied by Maxo.
This proves the verification material is available. It does not prove that Maxo is signing mail.
Delivered message
The receiver validates a DKIM signature whose d= domain matches the visible From domain.
This verifies the signing configuration and the public key together.
For a TXT selector, query the full selector hostname. For a CNAME selector, check the alias and the public key at its destination. Use the selector Maxo actually supplied.
Retest after a key rotation or sending-route change. Existing messages retain their original signatures, so send a fresh message for each check.
Set up DMARC
DMARC passes when SPF or DKIM passes with a domain matching the visible From domain. I keep the default relaxed alignment unless an established domain policy requires stricter matching.
- Check the current policy. Look up _dmarc at your sending domain. Retain an existing quarantine or reject policy and its reporting destinations; do not replace it with the starter record below.
- Choose reporting. Create a mailbox that accepts aggregate report attachments, or use the report address assigned by your reporting platform. Replace the example address with that working destination.
- Publish one record. For a new deployment, create one TXT record at _dmarc with p=none. If the DNS editor adds example.com automatically, enter only _dmarc in its hostname field.
- Validate the result. Check the published policy and reporting address. If reports go to another domain, confirm the reporting provider has configured external-destination authorization.
Use our DMARC record generator to prepare the TXT value. The starter record below is for a domain without an existing DMARC enforcement policy.
Replace example.com and dmarc@example.com with your domain and report mailbox. The example mailbox is a placeholder, not a report collection service.
Starter DMARC record for a new deploymenttext
Name: _dmarc.example.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com
The p=none policy requests monitoring without DMARC quarantine or rejection. It does not disable the receiver's spam filtering.
Enter the visible From domain below to check the published record. This DNS check is separate from testing whether a specific Maxo message passes authentication.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Confirm the result contains your intended policy and report destination. Correct duplicate DMARC records and hostname mistakes before relying on the results.
Reports arrive after participating receivers process mail and compile their reporting periods, commonly daily. Send a test message now to validate the sending configuration without waiting for reports.
Verify and troubleshoot
I test through the exact Maxo service used in production. A message sent through another mailbox or relay tests that route instead.
- Send a real message. Use the email tester below, copy its test address and send to it through your Maxo service. For service-generated notifications, trigger that notification rather than sending through an unrelated mailbox.
- Read receiver results. Check Authentication-Results for spf=pass, dkim=pass and dmarc=pass. Confirm the envelope domain and DKIM signing domain match the visible From domain as required.
- Check DNS visibility. Query your authoritative nameservers and a recursive resolver. Compare record names and values, then allow cached answers to expire according to the previous TTL.
- Escalate with evidence. Give Maxo the message timestamp, Message-ID, receiver results and outbound IP. Include the configured return path and selector, with credentials removed.
The email tester gives a diagnosis of the message you send, including authentication results. It is the quickest check of the configuration used by that actual message.
If Maxo generates different message types, test each relevant sending route. A successful test for one route does not validate another route with different servers or signing settings.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
SPF alignment failures alone do not mean DMARC failed. A valid DKIM signature with a matching domain is sufficient for a message-level DMARC pass.
Use the failure result to choose the fix. Authentication success also does not guarantee inbox placement; recipient filtering considers other signals.
|
|
|
|---|---|---|
SPF permerror | Duplicate or limit | Repair SPF |
SPF mismatch | Wrong return path | Ask Maxo to apply |
DKIM absent | Signing disabled | Enable signing |
DKIM key error | Wrong selector | Check supplied DNS |
DKIM body error | Message modified | Inspect mail route |
DMARC fail | No matching pass | Check both domains |
Troubleshoot the result reported by the receiving server.
For MaxoTel email-to-fax, the documented Secure Email option checks the SPF of the email you send into Maxo. Fix authorization for the service sending that request. This check does not configure DKIM on Maxo-generated outbound mail.
If an outbound IP has a blocklist (blacklist) listing, investigate that separately with Maxo. Correct authentication does not remove an IP listing.
Get alerted when it breaks
Suped is our DMARC platform for ongoing DMARC monitoring. It groups aggregate reports by sending source and identifies authentication issues, so a Maxo configuration that stops working is visible after the initial test.
- Route reports. Keep the Suped reporting address assigned to your domain in rua. Preserve other required report destinations when updating the existing DMARC record.
- Enable notifications. In Suped notification settings, enable Issues detected and Sending sources need verification. Enable DMARC summary emails for periodic review.
- Review Maxo traffic. Confirm that Maxo is an authorized sender before marking the source verified. Inspect its SPF and DKIM results against the expected domains.
- Resolve and retest. Use the issue-specific fix steps, correct the DNS or Maxo configuration, then send a new test. Check later reports to confirm the affected traffic recovers.
Suped's issue detection and notifications make ongoing checks practical without repeatedly opening XML reports. Report-based alerts depend on receiver reporting schedules; they do not inspect every message at send time.
Source identification needs confirmation
An rDNS hostname ending in .maxo.com.au helps identify Maxo infrastructure. Confirm authorization using your account records and authentication domains before trusting the source or changing SPF.
Secure your domain with p=reject
I move to enforcement after legitimate sending routes are accounted for and tested. Use Suped's source-level history and issue diagnostics to check that Maxo and your other senders consistently authenticate with matching domains.
- Inventory legitimate mail. Account for employee mailboxes, invoices, website messages and other authorized senders. Review enough reporting history to include infrequent business messages.
- Fix DKIM first. Require working DKIM with a matching signing domain for Maxo traffic before p=reject. SPF alone is fragile through forwarding and is insufficient for full participation under the current DMARC standard.
- Stage enforcement. For a new deployment, move from p=none to p=quarantine, review legitimate failures, then use p=reject. Keep existing enforcement while correcting a specific Maxo issue.
- Review subdomains. Check inherited policy and any explicit subdomain DMARC records. Test each active From subdomain before enforcing rejection across the domain.
- Keep monitoring. Retain aggregate reporting and Suped alerts after enforcement. Review new sending sources and retest after DNS changes or Maxo sending-route changes.
Our Hosted DMARC lets you manage policy changes in Suped after its DNS delegation is configured. Pair those controls with source-level reports to make each enforcement change based on observed legitimate traffic.
The record below shows the final policy for a directly managed TXT deployment. Use your working reporting address and preserve other necessary tags. With Hosted DMARC, make the equivalent policy change in Suped.
Final DMARC policy after verificationtext
Name: _dmarc.example.com Type: TXT Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com
A p=reject policy requests rejection of mail that fails DMARC. Receiving systems apply their own handling rules, so the policy is not a guarantee that every failing message is rejected.
If legitimate failures appear after a policy change, inspect the affected source and message route immediately. Keep the reporting destination active so the evidence needed to fix the problem remains available.
Frequency asked questions
Get the approved include hostname or outbound IP mechanisms from Maxo for your service. Its public support material does not establish a universal customer include. Do not assume include:maxo.com.au is correct or copy Maxo's corporate SPF record.
DNS is only one part of DKIM. Maxo must support signing for your domain and sign messages using the private key corresponding to the published selector. Ask support to confirm availability and enablement for your service, then verify a fresh message.
An SPF pass authenticates the envelope-sender domain. DMARC also requires that domain to match the visible From domain under the configured alignment mode. If DKIM also lacks a passing signature with a matching domain, DMARC fails. Ask Maxo to apply its supported custom return path and verify DKIM.
Suped identifies the .maxo.com.au rDNS suffix with Maxo, also branded MaxoTel. The suffix identifies infrastructure, not whether a message is authorized to use your domain. Check the outbound IP and authentication domains against your Maxo service before approving the source.
Keep an existing p=reject or p=quarantine policy while fixing Maxo authentication. The p=none starter record is for new deployments without enforcement. Diagnose the specific failing route and retest it before changing the domain-wide policy.
Check authoritative DNS after saving the records, then test a new message after the receiving resolver can see the updated values. Cached answers follow their previous TTL. Aggregate DMARC reports arrive on receiver schedules, commonly daily, so use the email tester for the initial message check.

