Suped

How to set up DMARC/DKIM/SPF for Enreach

Published 10 Jul 2026
Updated 11 Nov 2026
14 min read
Summarize with
Enreach SPF, DKIM, and DMARC setup for authenticated email.
Updated on 11 Nov 2026: We added the documented Swyx mail-server setup and corrected DKIM requirements for p=reject, DNS verification, and external DMARC reporting.
Enreach covers several products and sending paths, so its authentication values are not universal. For any Enreach workflow that uses your domain in the visible From address, identify the actual outbound mail path first, publish only the values that apply to it, and verify a real message. Start DMARC monitoring at p=none unless the domain already has p=quarantine or p=reject. Test Enreach under the existing policy before enabling its production mail flow.
What has to pass
  1. SPF: The sending IP must pass SPF for the envelope sender domain, and that domain must match the visible From domain under DMARC alignment rules for an SPF-based pass.
  2. DKIM: If the Enreach workflow supports branded signing, DKIM must pass with a d= domain aligned to the visible From domain.
  3. DMARC: DMARC passes when at least one authenticated identifier, SPF or DKIM, passes with an identifier matching the visible From domain under DMARC rules.
  4. Reports: Aggregate reports show which sources use your domain and whether their SPF, DKIM, and DMARC checks pass.

Identify the Enreach sending path

Start with the Enreach product and the exact message workflow. Swyx Operator welcome emails sent through Enreach's default infrastructure need a different DNS decision from Enreach software configured to submit mail through your own SMTP relay.
  1. Swyx Operator default relay: Enreach's Swyx Operator SPF instructions authorize smtp.ispworks.net with the SPF a mechanism for partner-account and SwyxMeeting welcome emails. This is not an include mechanism.
  2. Customer SMTP relay: If Enreach submits through a relay you control, that relay determines the envelope sender, DKIM signature, sending IP, and required DNS records.
  3. Microsoft 365 mail mode: Swyx 14.25 introduced sending through Exchange Online using the Microsoft Graph API. Enreach documents this integration; use that mail path's authentication settings rather than the Swyx Operator SPF value.
  4. Other Enreach products: Obtain product-specific values from the current admin screen, reseller, or Enreach support instead of reusing the Swyx Operator SPF value.
  5. Separate workflows: Test each type of invitation, notification, voicemail, or campaign message because one Enreach deployment can use more than one mail path.
Swyx Operator SPF example, only when no SPF existsDNS
Name: example.com Type: TXT Value: v=spf1 a:smtp.ispworks.net -all
One value does not cover every Enreach product
The cited Enreach instructions document this SPF value for Swyx Operator welcome emails. That article does not supply DKIM selectors, return-path targets, or verification tokens; obtain any required values for your actual sending path.

Confirm your sending domain and DNS access

If your Enreach product has a sender-domain or outbound-mail screen, start there because verification records can vary by product, tenant, and region. If it does not expose those controls, collect the same values from your reseller or Enreach support. Confirm which provider hosts your authoritative DNS zone and ensure you can edit it. Use the hostname format that provider expects; enter _dmarc rather than _dmarc.example.com when the editor automatically appends example.com.
  1. Identify the product: Record the Enreach product, tenant, region, and message workflow before changing DNS.
  2. Find mail controls: Open its sender-domain, email, notification, or SMTP settings, or ask support for the applicable authentication instructions.
  3. Confirm the From domain: Use the organizational domain or sending subdomain that appears in the visible From address.
  4. Copy issued records: Copy every hostname and value shown for verification, DKIM, SPF, or return-path without changing the target.
  5. Verify with mail: After the records resolve publicly, complete any applicable Enreach verification action and inspect a real message header. Cached answers expire according to DNS TTL, so check the published name and value before repeating a change.
Illustrative Enreach sending-domain verification screen with DNS record fields.
Illustrative Enreach sending-domain verification screen with DNS record fields.
Do not guess vendor records
Treat every DKIM selector, verification token, and return-path hostname as product-specific until Enreach or the configured SMTP relay confirms it. A plausible-looking record can validate in DNS while authenticating nothing.
Illustrative record shapes, not Enreach valuesDNS
_verification.example.com. TXT "REPLACE_WITH_ISSUED_TOKEN" bounce.example.com. CNAME REPLACE_WITH_ISSUED_RETURN_PATH_TARGET selector1._domainkey.example.com. CNAME REPLACE_WITH_ISSUED_DKIM_TARGET

Configure the Swyx mail server

In Swyx Control Center, open General Settings > System > Mail Server. The Enreach mail-server instructions document these controls for Swyx; other Enreach products use their own settings.
  1. Select the mail mode: Choose SMTP for your relay or Microsoft 365 (Exchange Online) for that integration. Off disables the email functions that depend on this configuration.
  2. Configure SMTP: Enter the mail-server address and port, then configure authentication and Use SSL as required by the relay. Use a sender address whose domain is managed by that mail server.
  3. Configure Microsoft 365: Set up Microsoft Entra ID federation and grant the required Mail.Send API permission, then specify the sender address. Configure SPF and DKIM for the domain in Exchange Online.
  4. Test and save: Click Send test email, inspect the delivered message, then click Save. Check Overview > E-mail queue when messages remain queued or fail to send.
A successful SMTP login or Graph API submission does not prove DMARC success. Verify the receiving mail server's authentication results for each production workflow.

Set up SPF

SPF authenticates the envelope sender domain, which appears in Return-Path after delivery. Enreach's published Swyx Operator instruction uses a:smtp.ispworks.net. Use that mechanism only for the documented Swyx Operator workflow. For another Enreach product or a customer-managed SMTP relay, use the value issued for that path. Publish SPF for the envelope sender domain you control; changing the visible From domain's SPF does not change checks against a different Return-Path domain.
  1. Read Return-Path: Send an Enreach message and record the envelope sender domain used for SPF.
  2. Use the correct record: Add a:smtp.ispworks.net for the documented Swyx Operator path when your domain is the envelope sender. For another relay, follow its issued SPF or custom Return-Path instructions.
  3. Merge once: Add the mechanism before the existing all term in the domain's single SPF record instead of creating a second SPF record.
  4. Count lookups: RFC 7208 limits SPF evaluation to 10 DNS-querying mechanisms and modifiers, including those reached through nested includes and redirects. Exceeding this limit produces permerror; it is not a count of every individual DNS query.
  5. Preserve policy: Do not change -all to ~all merely to add Enreach. The terminal qualifier is a policy choice for every sender covered by that SPF record.
Swyx Operator SPF examplesDNS
Standalone example, only if no SPF exists: Name: example.com Type: TXT Value: v=spf1 a:smtp.ispworks.net -all Merge example, replace include:current.example with your existing mechanisms: v=spf1 include:current.example a:smtp.ispworks.net ~all

SPF checker

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

?/16tests passed
If your Enreach setup does not show a return-path control, do not assume one can be enabled. Inspect a delivered message and ask for product-specific guidance. DKIM can produce the aligned pass DMARC needs, but SPF should still describe the real envelope sender correctly.

Enreach value

DNS action

What to check

a:smtp.ispworks.net
Merge SPF
Swyx Operator path
Issued bounce CNAME
Add only the issued CNAME; no TXT at that name
SPF alignment
No issued value
Do not guess
Inspect header
Use only the value that matches the sending path.
SPF pass is not always a DMARC pass
SPF-based DMARC needs both SPF authentication and identifier alignment. A passing Enreach-owned Return-Path that does not match your visible From domain under DMARC rules will not carry DMARC. An aligned DKIM pass can still make DMARC pass.

Set up DKIM

Enreach's Swyx Operator SPF instructions do not provide DKIM records. If the selected Enreach workflow or your configured SMTP relay supports DKIM, sign with a d= domain aligned to the visible From domain and publish only the selector it issues.
  1. Find the signer: Confirm whether Enreach or your SMTP relay signs the specific message workflow.
  2. Copy selector: Record the s= selector, d= signing domain, full DNS hostname, record type, and value.
  3. Create record: Add the CNAME or TXT record exactly as issued, without adding your domain twice in the DNS host field.
  4. Enable signing: Complete any verification step, then enable DKIM for the same sender domain.
  5. Read header: Send a live message and confirm dkim=pass plus alignment between header.d and header.from.
Illustrative Enreach DKIM setup screen with selector and DNS record fields.
Illustrative Enreach DKIM setup screen with selector and DNS record fields.
CNAME DKIM
Use this form only when the sending system supplies a CNAME target.
  1. Host: Add the issued selector hostname under _domainkey.
  2. Target: Point it to the exact DKIM target shown for the sending path.
  3. Rotation: The target owner can rotate the public key without another DNS edit.
  4. Check: The CNAME resolves before you complete verification.
TXT DKIM
Use this form only when the signing system supplies a public key directly.
  1. Host: Publish the selector hostname exactly as shown.
  2. Value: Paste the full public key without smart quotes or unintended spaces.
  3. Risk: A missing character prevents signature verification.
  4. Check: A live message shows the expected d= and s= values with dkim=pass.
Illustrative DKIM record formsDNS
selector1._domainkey.example.com. CNAME REPLACE_WITH_ISSUED_DKIM_TARGET selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=REPLACE_WITH_ISSUED_PUBLIC_KEY"
Use DKIM before p=reject
A valid, aligned DKIM signature often survives forwarding when the signed message content remains unchanged. RFC 9989 requires valid DKIM signatures for domains publishing p=reject and prohibits relying solely on SPF. If the selected Enreach path cannot sign with your domain, ask Enreach about a supported signing relay before enforcing reject.

Set up DMARC

For a visible From domain of example.com, publish DMARC at _dmarc.example.com. An explicit policy for notifications.example.com belongs at _dmarc.notifications.example.com. For a domain without an existing policy, use p=none first and collect aggregate reports. If the domain already has p=quarantine or p=reject, verify Enreach under that policy before enabling production mail. The DMARC record generator assembles the record without manual tag editing.
Starting DMARC recordDNS
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
  1. Start at none: Use p=none with rua for a fresh monitoring start.
  2. Keep stricter: If the domain already uses quarantine or reject, fix the Enreach sending path and test it before enabling production mail. Avoid weakening policy for unrelated senders.
  3. Set reporting: Replace dmarc@example.com with an address that receives and processes aggregate XML reports. For Suped, copy the rua destination assigned to your domain. If the destination is outside your organizational domain, confirm its DNS authorization under RFC 9990.
  4. Publish once: Keep one DMARC policy record at each _dmarc hostname because multiple records at one target are discarded.
  5. Review subdomains: Check the inherited policy before adding a subdomain-specific record. The sp tag covers existing subdomains and np covers nonexistent subdomains of the organizational domain.

DMARC checker

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

?/7tests passed
After DNS propagation, the checker should show one valid DMARC record. The next proof is a live Enreach message where Authentication-Results shows dmarc=pass for the visible From domain.
Stage DMARC enforcement
RFC 9989 makes the pct tag historic. Stage a simple rollout with p=none, then p=quarantine, then p=reject after reviewing legitimate sources. Its t=y test mode requests policy handling one level below the published policy, rather than percentage sampling. Receivers that do not support t ignore it, so do not depend on it to prevent rejection. Receivers make the final delivery decision.

Policy

Use when

Requested handling

p=none
Discovering sources
No policy action
p=quarantine
Legitimate mail passes
Treat failures as suspicious
p=reject
Legitimate sources verified; DKIM signing enabled
Rejection subject to receiver policy
Choose policy after verifying legitimate Enreach traffic.
DMARC reports are not instant
Aggregate reports usually arrive on a daily cycle. Use live test messages for immediate validation and report data to confirm source coverage over time.

Verify authentication and alignment

Verification requires real message headers, not only a green DNS status. Trigger a normal Enreach notification, inspect the receiving mail server's Authentication-Results and the underlying identifiers, then compare the source with DMARC reports after the next reporting cycle.
  1. Send live mail: Trigger each Enreach workflow your users receive because templates and message types can use different paths.
  2. Record identifiers: Note the visible From domain, Return-Path domain, DKIM d= domain, and DKIM s= selector.
  3. Check SPF: Confirm spf=pass for the Return-Path and verify that domain has DMARC alignment with the visible From domain if SPF carries DMARC.
  4. Check DKIM: Confirm dkim=pass and verify that header.d has DMARC alignment with the visible From domain if DKIM carries DMARC.
  5. Check DMARC: Confirm dmarc=pass for header.from and identify whether the aligned SPF or DKIM result produced the pass.
Illustrative Enreach outbound email log with message authentication status.
Illustrative Enreach outbound email log with message authentication status.

Failure

Likely meaning

First check

SPF fail
Sending IP not authorized by SPF
Return-Path SPF
DKIM fail
Wrong key or altered message
d= and s= values
DMARC fail
No aligned pass
header.from alignment
SPF permerror
Duplicate record or excess lookups
SPF syntax and count
SPF temperror
Temporary DNS lookup failure
DNS availability; retry after recovery
Separate authentication failure from alignment failure.
Use the email tester below with a real Enreach message. It reads the headers and shows whether the authentication results satisfy DMARC.

Email tester

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

?/43tests passed
Fix the layer shown in the delivered header first. A DNS lookup proves that a record exists, while the header proves that the Enreach sending path used it and that the authenticated identifier aligned. With default relaxed alignment, bounce.example.com and example.com share the organizational domain. aspf=s requires an exact SPF domain match; adkim=s requires an exact DKIM domain match. See RFC 9989.
Example receiver header with relaxed SPF alignmenttext
Authentication-Results: mx.example; spf=pass smtp.mailfrom=bounce.example.com; dkim=pass header.d=example.com header.s=selector1; dmarc=pass header.from=example.com
A common false fix
Adding another SPF TXT record at the same hostname causes a permanent error. Merge the applicable Enreach mechanism into the existing record, then check syntax and lookup count.

Get alerted when authentication changes

Email authentication can break after mail-path migrations, DNS cleanups, selector rotations, or return-path changes. Suped is our DMARC monitoring and email authentication platform. For this workflow, it groups aggregate data by source, monitors DNS state, and alerts you when incoming data shows that Enreach authentication changed. Compare grouped sources with the Enreach workflow you tested. Aggregate-report alerts follow incoming report data rather than each individual send.
Enforcement decision
Judge legitimate sources separately from unauthorized traffic because spoofing can distort an overall pass rate.
Ready
Verified sources
Enreach and every other legitimate source consistently pass DMARC, with valid DKIM signing configured before reject.
Investigate
Fix first
An expected Enreach workflow still fails authentication or alignment.
Do not enforce
Classify source
A source that might be legitimate has not been classified or tested.
What to alert on
  1. New source: A new IP or host starts sending with your domain.
  2. DKIM drop: Enreach traffic stops signing, fails verification, or uses an unaligned domain.
  3. SPF change: Return-Path authorization or alignment changes after a routing update.
  4. Policy risk: A legitimate source fails while the domain requests quarantine or reject.

Move to p=reject after testing

A reject policy is appropriate after Enreach and every other legitimate sender are identified, consistently pass DMARC, and have valid DKIM signing configured. Suped's Hosted DMARC lets teams manage policy changes without repeated manual DNS edits.
Unsafe jump
  1. No inventory: Enreach is added without checking existing senders.
  2. No headers: DNS looks correct, but no real Enreach message was inspected.
  3. No staging: The domain jumps straight to reject while legitimate sources still fail.
  4. No monitoring: A later Enreach change is noticed only after delivery is affected.
Controlled enforcement
  1. Source map: Each Enreach path is listed with every approved sending source.
  2. Header proof: Live messages show dkim=pass with a signing domain that satisfies DMARC alignment.
  3. Policy stages: Monitoring at none is followed by quarantine, then reject.
  4. Ongoing checks: Reports and DNS monitoring continue after enforcement.
Move to reject only after each legitimate Enreach mail path has stable aligned authentication and aggregate reports show no approved source failing DMARC. An overall failure rate that includes unauthorized mail is not a reason to delay enforcement.
  1. Cover a full cycle: Monitor long enough to include routine and low-frequency senders, not only one successful Enreach test.
  2. Fix legitimate mail: Configure valid DKIM signing for every approved Enreach workflow before p=reject, and verify DMARC alignment in delivered messages.
  3. Stage whole policies: Move from p=none to p=quarantine, then p=reject without using the historic pct tag.
  4. Account for mailing lists: RFC 9989 advises against p=reject for domains whose users post to Internet mailing lists. If proceeding, compare at least a month of p=none reports with an equally long p=quarantine period before reject.
  5. Keep reporting: Leave aggregate reporting active after reject so Enreach regressions remain visible.
Final reject policyDNS
Name: _dmarc.example.com Type: TXT Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Reject needs monitoring after launch
A working Enreach setup can break after a product migration, DNS cleanup, or key rotation. Suped can keep the source and authentication result visible after enforcement so the changed path can be identified.

FAQ

Use SPF and DKIM when the selected Enreach mail path supports them, then publish DMARC for the visible From domain. DMARC needs at least one aligned pass, but configuring both authentication methods gives the message another valid path to pass.

For the Swyx Operator partner welcome-email workflow documented by Enreach, add a:smtp.ispworks.net to the domain's single SPF record. For another Enreach product or a customer-managed SMTP relay, use its issued value and confirm the Return-Path in a live message.

Enreach's Swyx Operator SPF article does not provide DKIM records. Use the CNAME or TXT record issued by the selected Enreach product or by the SMTP relay that signs its mail, then confirm the d= and s= values in a live header.

DMARC still passes through DKIM when the signature validates and its d= domain has DMARC alignment with the visible From domain. Fix SPF separately by checking the real Return-Path, applicable mechanism, syntax, and DNS lookup count.

Move to reject after every legitimate Enreach workflow and other approved source consistently passes DMARC in live tests and aggregate reports, with valid DKIM signing configured. Assess forwarding and mailing-list effects, and keep reporting active after enforcement.
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