Suped

How to set up DMARC/DKIM/SPF for Adista

Published 21 Nov 2026
Updated 21 Nov 2026
11 min read
Summarize with
Adista email authentication setup with SPF, DKIM, and DMARC.
Set up Adista email authentication by authorizing the actual outbound relay in SPF, enabling DKIM signing with your domain, and publishing a DMARC TXT record at your From domain's _dmarc name. DMARC passes when either SPF or DKIM passes with a domain that matches the visible From domain under your DMARC alignment settings.
I start with the Adista service details and a real outbound message. Adista supports a custom Return-Path, so request that configuration alongside DKIM. The SPF authorization and DKIM records must match your contracted sending service; the settings for Adista's own corporate email are not a customer configuration.

Add your domain

Have Adista provision your sending domain on the mail service or relay covered by your contract. If the domain already sends through Adista, ask support to confirm its current authentication settings before making changes.
  1. Identify the service. Sign in to your existing Myadista customer portal and contact technical support for the relevant mail service. Supply your customer reference and the exact From domain, such as example.com.
  2. Request the settings. Ask for the outbound relay details, the approved SPF include or sending IPs, a custom envelope sender domain, and the DKIM selector with its complete DNS record.
  3. Verify ownership. Complete the ownership check Adista requests. If support issues a DNS challenge, publish its exact name and value in your authoritative DNS zone, then ask Adista to verify it.
  4. Confirm activation. Have Adista confirm that the domain is authorized for sending and that the requested Return-Path and DKIM signing are active. Send a message through the real application to verify the result.
Adista's published support contacts are stc@adista.fr for technical support and support-ndd@adista.fr for domain support. Use domain support when Adista manages the DNS zone and you need records published.
I could not verify a public Adista walkthrough for adding domains or enabling DKIM. Treat domain verification as service-specific: obtain the required proof and records through your account contact, rather than assuming a shared verification token or menu path.

Task

Responsible party

Required result

Domain provisioning
Adista support
Sending authorized
DNS publication
DNS administrator
Records visible
DKIM signing
Signing server owner
Signature enabled
Message testing
Application owner
DMARC passes
Confirm these responsibilities before publishing records.

Set up SPF

SPF authorizes the server sending the message for the SMTP MAIL FROM domain, which normally appears in the delivered Return-Path. Publishing SPF only at example.com does not authorize a separate envelope domain such as bounce.example.com.
  1. Set the envelope domain. Ask Adista to use example.com or a dedicated subdomain such as bounce.example.com as your custom MAIL FROM domain. Keep bounce handling configured as Adista requires.
  2. Confirm the authorization. Ask whether your service uses include:protect.smtpout.adista.fr. Use that include only when Adista confirms it covers your outbound route; otherwise use the service-specific authorization supplied.
  3. Edit one SPF record. At the actual MAIL FROM domain, merge the confirmed authorization into the existing v=spf1 TXT record before its final all mechanism. Preserve every other legitimate sender.
  4. Check the lookup limit. Keep SPF within the limit of 10 DNS lookup-causing terms during evaluation, including nested includes. Multiple SPF records at the same name produce an error.
Conditional example: only when Adista confirms this include and is the sole sendertext
Name: bounce.example.com Type: TXT Value: v=spf1 include:protect.smtpout.adista.fr -all
Replace bounce.example.com with your actual envelope sender domain. The example's -all assumes the record lists every authorized sender for that domain. If Adista supplies a CNAME delegation for the envelope domain, publish that delegation exactly; do not also place a TXT record at the same name.
Enter the envelope sender domain in the SPF checker to inspect the published record and its lookup usage. Check the root domain separately if another sending stream uses it for MAIL FROM.

SPF checker

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

?/16tests passed
After DNS caches expire, send a fresh message through Adista. Confirm spf=pass and inspect smtp.mailfrom in the receiving server's Authentication-Results header to establish which domain was checked.
A Return-Path under bounce.example.com matches a From address at example.com with relaxed SPF alignment. Strict SPF alignment requires an exact domain match. If your specific service retains an Adista-owned Return-Path, adding Adista to your root SPF will not fix SPF alignment; DMARC can still pass through a valid DKIM signature using your domain.

Set up DKIM

Ask Adista to enable DKIM signing with your From domain, or a matching subdomain under relaxed DKIM alignment. Request a 2048-bit RSA key with rsa-sha256 where the service supports it.
  1. Obtain the selector. Get the exact selector, signing domain, DNS record type, and complete public value or CNAME target. There is no verified universal Adista selector to copy.
  2. Publish the record. Create the supplied record at selector._domainkey.signing-domain. If your DNS editor appends the zone name automatically, enter only the relative hostname it expects.
  3. Activate signing. After the record resolves publicly, ask Adista to validate it and activate signing for your domain. A DNS key by itself does not cause messages to be signed.
  4. Check a fresh message. Read d= and s= in DKIM-Signature, then confirm dkim=pass in the recipient's trusted authentication results. The signing domain must match your From domain under the configured alignment mode.
If Adista supplies TXT
Publish the complete public key at the assigned selector name. Keep the private key on the signing server. Preserve the entire public value, including any DNS string splitting required by your DNS host.
If Adista supplies CNAME
Publish the exact selector alias and target Adista provides. Do not add a TXT record at the same name. Confirm that the alias ultimately resolves to the intended DKIM public key.
If the contracted relay does not provide customer-domain DKIM signing, enable signing on your application or mail server before it relays through Adista. Confirm that the relay preserves the signed content and that the recipient verifies the signature.
Use the actual selector and signing domain from your configuration or message header in these DNS checks. A successful lookup confirms publication; a received message with dkim=pass confirms signature verification.
Look up the assigned DKIM selectorbash
DKIM_SELECTOR=replace_with_assigned_selector SIGNING_DOMAIN=example.com dig +short CNAME "${DKIM_SELECTOR}._domainkey.${SIGNING_DOMAIN}" dig +short TXT "${DKIM_SELECTOR}._domainkey.${SIGNING_DOMAIN}"

Set up DMARC

Publish DMARC in your domain's authoritative DNS, independently of where Adista hosts the application or relay. If your existing policy is p=quarantine or p=reject, keep that policy while fixing Adista authentication.
  1. Inspect the existing policy. Look up _dmarc.example.com. Edit an existing DMARC record instead of creating a second one at the same name.
  2. Start new policies in monitoring mode. If no DMARC policy exists, create one TXT record at _dmarc.example.com with the value shown below. In a DNS editor for example.com, the host field is usually _dmarc.
  3. Configure reporting. Replace the example reporting address with a mailbox you control or your assigned aggregate-report destination. The DMARC record generator can build the record with those settings.
Initial DMARC TXT value for a domain without an enforcement policytext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
The example address is a placeholder. A mailbox receives aggregate XML reports but does not automatically analyze them. A reporting destination on another domain also needs the external reporting authorization required by DMARC.
Check the visible From domain in the DMARC checker. If you send as billing@mail.example.com, inspect that subdomain as well as its parent policy so you understand the policy the receiver discovers.

DMARC checker

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

?/7tests passed
A valid DMARC DNS record confirms publication and syntax. It does not prove that Adista signs messages correctly or uses your intended envelope sender. Verify both with an actual message.
The p=none policy requests monitoring without asking receivers to quarantine or reject messages because of DMARC failure. Aggregate reports commonly arrive daily, and some receivers do not send them.

Verify and troubleshoot

I test the actual sending workflow after configuration: trigger an application notification or send through the same Adista relay used in production. A test sent through a different mail service does not verify that path.
The email tester is the quickest message-level check. It provides a destination address; send a fresh message there through Adista to get a full diagnosis of authentication and other delivery checks.

Email tester

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

?/43tests passed
Expect dmarc=pass, with at least one passing authentication method using a domain that matches the visible From domain. Aim for both SPF and DKIM to pass on direct delivery. SPF alignment errors are acceptable for DMARC when a valid DKIM signature has the required domain match.
Use Authentication-Results added by the receiving system you trust. A sender-provided authentication header or a DKIM-Signature header without a verification result is not evidence that authentication passed.
  1. Fix SPF errors. For permerror, merge duplicate SPF records and reduce excessive lookup-causing terms. For fail, compare the observed sending IP with the authorization Adista confirmed.
  2. Fix DKIM errors. For a missing key, check the exact selector and DNS hostname. For signature failures, ask Adista to check the active key and any message changes after signing.
  3. Fix domain mismatches. Compare the visible From domain with smtp.mailfrom and the passing DKIM signature's domain. A valid signature using adista.fr alone does not authenticate a From address at example.com for DMARC.
  4. Retest every route. Repeat after the relevant DNS TTL expires and send through each application's production path. Include failover routes and forwarded messages in the checks.
Check DNS publication using your real domainbash
dig +short NS example.com dig +short TXT example.com dig +short TXT bounce.example.com dig +short TXT _dmarc.example.com
Keep the delivered message headers and the DNS results with your Adista support request. Include the timestamp and source IP so support can trace the specific relay and signing configuration.

Get alerted when it breaks

Our DMARC platform, Suped, connects aggregate report analysis with authentication issue detection and notifications. For Adista mail, that gives your team a way to investigate a changed relay, a broken DKIM selector, or an unexpected sending source.
Once aggregate reports are flowing to Suped, use DMARC monitoring to review Adista traffic alongside every other sender using your domain. Confirm which sources your organization authorizes before treating a source as legitimate.
  1. Enable issue notifications. In Suped's notification settings, enable Issues detected and Sending sources need verification. Enable DMARC summary emails for regular review.
  2. Verify Adista sources. Match the reported IPs and authentication domains to your Adista service details. Verify recognized sources after confirming that your organization uses them.
  3. Investigate the failure. Open the detected issue and its steps to fix. Inspect the detailed SPF, DKIM, and DMARC results, then send the relevant evidence to the DNS owner or Adista support.
  4. Confirm recovery. Run another message test after the fix and check subsequent report periods. Review DNS history when the issue follows a record change.
I keep the DNS owner and the Adista service owner involved in issue review. A relay change needs a different fix than an accidentally deleted selector, even when both first appear as a DMARC failure.
Keep periodic test sends for important application workflows. DMARC aggregate reports describe mail observed by reporting receivers; they do not confirm that an application is still sending.
Report timing affects alert timing
Suped can notify you about issues it detects in received data. DMARC aggregate reports are delayed, so these notifications are not immediate detection of every failed message. Use live message tests when investigating an active incident.

Secure your domain with p=reject

Move to p=reject after your legitimate sending streams consistently pass DMARC and you have tested important indirect delivery paths. I base that decision on identifiable sources and representative traffic, rather than a single successful test.
Suped's source verification and detailed authentication results help establish which failures belong to legitimate Adista traffic. Our Hosted DMARC lets you manage the policy through Suped once configured, with reports available to assess each policy change.
  1. Inventory legitimate senders. Review Adista and every other service using the From domain. Confirm each source with its application owner; do not authorize an unfamiliar source merely because it appears in reports.
  2. Repair authorized traffic. Get matching DKIM working for each Adista workflow and configure matching SPF where supported. Remove obsolete authorizations only after confirming the service is retired.
  3. Observe a full sending cycle. Include infrequent billing runs, alerts, and failover routes. Test forwarding and mailing lists: SPF checks the forwarder's IP, and message edits can invalidate DKIM.
  4. Stage enforcement. For a domain starting at p=none, move to p=quarantine after resolving legitimate failures and review subsequent delivery results. For domains used with mailing lists, allow at least a month in each observation stage and resolve any legitimate list traffic failures before proceeding.
  5. Apply rejection. Change the existing policy to p=reject when the evidence supports it. Preserve reporting, review subdomain policies including any sp setting, and keep Suped notifications enabled after the change.
Final DMARC TXT value after validating legitimate traffictext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Rejection has a specific scope
The p=reject policy asks receivers to reject messages that fail DMARC, subject to their local handling decisions. It does not guarantee inbox delivery or prevent impersonation through a different domain.
Replace the example reporting address with your working destination. If a domain is already at p=reject, preserve enforcement and fix the failing Adista stream; a new sender is not a reason to weaken the whole domain's policy.
If legitimate traffic breaks during a policy change, identify the affected route, correct its authentication, and retest it. Do not add an unrecognized IP to SPF just to increase a pass rate.

Frequency asked questions

Ask Adista to confirm the include for your outbound service. If support confirms protect.smtpout.adista.fr, merge include:protect.smtpout.adista.fr into the SPF record at the actual MAIL FROM domain. A dedicated server or another Adista service needs the authorization assigned to that route.

Obtain the selector from Adista's configuration for your domain, or read s= in a message's DKIM-Signature header. Pair it with d= from that same signature to locate the DNS key. There is no verified universal selector to assume.

Yes. A passing DKIM signature whose signing domain matches your visible From domain under your DMARC alignment settings is sufficient. Adding an SPF record at your From domain cannot change an Adista-owned Return-Path. Request a custom envelope domain if you also need SPF alignment.

These suffixes are associated with Adista infrastructure. Examples include smtp12.adista.fr and smtp-01.smtpout.adista.fr. A hostname does not establish which customer sent a message or whether it was authorized. Compare the source IP and authentication results with the relay details confirmed by Adista.

Changing the root domain's inbound MX records is not a requirement for publishing SPF, DKIM, or DMARC. Follow Adista's instructions if its custom bounce domain needs separate routing records. Treat any migration of inbound email as a separate change.

Keep an existing p=reject or p=quarantine policy while configuring Adista. Resolve the new sending stream's SPF and DKIM settings and test it before production use. Use p=none as the initial monitoring policy for a domain without an existing enforcement policy.
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