How to set up DMARC/DKIM/SPF for Pronto
Published 18 Aug 2026
Updated 23 Oct 2026
12 min read
Summarize with

Updated on 25 Oct 2026: We corrected Pronto's relay authentication steps and replaced outdated DMARC percentage sampling.
Pronto Xi does not have one universal SPF record or DKIM key for every customer. It sends through the SMTP or cloud mail route configured in Pronto Xi TrueForm Neo. Authenticate that route, configure a custom Return-Path when supported, enable DKIM signing, and publish DMARC for the visible From domain.
First identify the server that transmits invoices, statements, alerts, and other Pronto messages. Pronto Xi 780 also supports cloud email through TrueForm Neo 3.4. That outbound route supplies the SPF authorization and DKIM DNS values; complete any domain verification required by the mail provider.
Configuration boundary
Pronto Xi composes the message and hands it to the configured mail route. The relay controls the envelope sender, DKIM signature, sending IP, and reverse DNS. Copy DNS values from that relay's current configuration rather than inventing Pronto-specific values.
Prepare the sending route and DNS
Before editing DNS records, confirm the Pronto workflow and mail route in use. Arrange access with the Pronto administrator and the owner of the authoritative DNS zone.
- Edit records where the domain's authoritative nameservers host its DNS zone. The domain registrar is only the right place if it also hosts that zone.
- Collect the relay's exact SPF instructions and DKIM selector records. Use the values for your own sending domain, rather than another product's sample records.
- For a connected cloud mailbox, complete the provider's domain verification and confirm that the account can send using the intended From address. Mailbox sign-in does not configure SPF or DKIM.
- Check whether the DNS editor automatically appends the domain name. For example, enter _dmarc or selector1._domainkey when the editor supplies .example.com, so the domain is not added twice.
Set up SPF
SPF authorizes the relay's sending IP through a record at the envelope-sender domain, shown in the Return-Path after delivery. Trace the outbound route in the Pronto workflow, then publish the relay's supplied SPF instructions at that domain.
- Open the workflow. In TrueForm Neo Builder, open the procedure that sends the document or notification and select the Send an email with security component.
- Record the route. Note Server Address, Enable SSL, Port Number, the From address, and any authenticated account. Pronto Xi versions and deployments can expose these settings differently.
- Set the Return-Path. If the relay supports it, configure a custom envelope-sender domain under your organizational domain. Confirm the actual Return-Path in a delivered message; changing the visible From address alone does not change it.
- Publish one record. For a relay that supplies an SPF TXT value, merge its include mechanism or sending IP into the existing record before the final all mechanism. Never create a second SPF record at that hostname.
- Check the lookup count. Limit evaluated DNS-querying terms to 10, including nested includes and redirects. The a, mx, exists, and ptr mechanisms also count; ip4, ip6, and all do not. See RFC 7208 for the lookup rules.

Pronto Xi TrueForm Neo Builder SMTP server and port settings
The example below shows the TXT approach. Replace the placeholder with the exact include hostname supplied by the relay owner and preserve other approved senders. If the relay instead supplies a CNAME for a dedicated bounce subdomain, publish that CNAME as instructed; do not add a TXT record at the same hostname.
SPF structure, replace the placeholderDNS
v=spf1 include:spf.your-relay.example ~all
An SPF pass alone is not enough for DMARC. The Return-Path domain must share the same organizational domain as the visible From address under relaxed alignment, or match it exactly with aspf=s. An SPF record at example.com is not automatically inherited by bounce.example.com.
If the route cannot use your domain in the Return-Path, use passing DKIM with DMARC alignment. Adding the relay to SPF at the visible From domain does not repair a different Return-Path domain's alignment.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Run the SPF check against the exact Return-Path domain found in a delivered Pronto message. A check of the visible From domain can look healthy while the envelope domain uses a different record.
After DNS updates, send a fresh document through the same TrueForm Neo procedure. Old messages prove only the earlier configuration, and cached results can persist until the record's TTL expires.
Set up DKIM
DKIM setup normally takes place on the outbound relay or connected mail route. Enable signing for the sending domain there, then publish the selector record it provides in DNS.
- Create the key. In the relay used by Pronto, enable DKIM for the domain in the visible From address and generate a selector. Use a 2048-bit key when the relay supports it.
- Publish the selector. Add the exact TXT or CNAME record returned by the relay at selector._domainkey.yourdomain.com, using the supplied selector and signing domain. Do not place the key at the root domain.
- Enable signing. Confirm the route signs every Pronto message, including scheduled alerts, statements, invoices, and test sends.
- Check the signing domain. Read d= and s= in DKIM-Signature, then confirm dkim=pass for that signature in the receiving server's Authentication-Results. The d= domain must share the From domain's organizational domain under relaxed alignment, or match exactly with adkim=s.
Pronto Xi controls
- Message identity. The workflow selects the From address, recipient, subject, and content.
- Delivery route. The email component points to the SMTP or cloud sending route.
Mail route controls
- Authentication. The route applies the DKIM signature and envelope sender.
- Network identity. The route supplies the sending IP, HELO name, and rDNS.
A relay can return a TXT public key or one or more CNAME targets. Publish every supplied selector using its exact record type, and do not put TXT and CNAME records at the same selector hostname. The shortened value below shows placement only and is not a usable key.
DKIM placement exampleDNS
selector1._domainkey.example.com TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY_FROM_RELAY"
Do not copy a DKIM key
Use the selector and public key supplied for your sending domain and route. A key copied from another environment fails if it does not match the private key used to sign the message.
Send one message for every Pronto workflow that uses a different From address or relay. A statement procedure can pass while an alert procedure fails if they use separate sending components.
Set up DMARC
DMARC evaluates the visible From domain and applies to Pronto plus every other sender using that domain. Start with monitoring when there is no effective DMARC policy, collect reports, and preserve an existing quarantine or reject policy while configuring Pronto.
- Choose the hostname. For mail sent as user@example.com, publish the TXT record at _dmarc.example.com.
- Create the mailbox. Make sure dmarc@example.com can receive aggregate reports, or replace it with a reporting address you actively process.
- Publish one policy. Add the record as TXT and remove any duplicate DMARC records at the same hostname.
- Preserve enforcement. If the domain already uses p=quarantine or p=reject, keep that policy and fix Pronto authentication without downgrading protection.
Initial DMARC monitoring recordDNS
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use Suped's DMARC record generator when the reporting address or policy needs to differ. For a domain without an existing or inherited policy, p=none requests monitoring without asking receivers to quarantine or reject failures. Other receiver filtering still applies.
DMARC passes when either SPF passes with alignment or DKIM passes with alignment. Both do not have to pass. Configure both where supported, and retain valid DKIM signing before considering p=reject because forwarding often breaks SPF.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Check the exact domain in the From header. For invoices.example.com, inspect _dmarc.invoices.example.com and any inherited policy before adding a record. Confirm the effective policy and intended reporting address rather than checking only example.com or the Pronto server hostname.
A valid DNS record does not prove that Pronto messages pass DMARC. Inspect a newly delivered message for its Return-Path, DKIM selector, and authentication results, then use aggregate reports to confirm source IPs and alignment results across traffic.
If rua points to an external reporting domain, that destination must authorize reports for your policy domain. Follow the destination's DNS instructions; without authorization, receivers ignore that reporting address. This requirement is defined in RFC 9990.
Verify and troubleshoot
Verify the full message path. Run the Pronto procedure, confirm TrueForm Neo reports a successful handoff, then inspect the receiving server's Authentication-Results for SPF, DKIM, and DMARC results. A passing result does not guarantee inbox placement.

Pronto Xi TrueForm Neo Event Viewer showing an SMTP handoff test
A successful Pronto event means the relay accepted the message. It does not prove the receiver accepted it or that DMARC passed, so continue through the received headers and report data.
|
|
|
|---|---|---|
SPF pass | Envelope source allowed | Check alignment |
DKIM pass | Signature valid | Check d= domain |
DMARC fail | No SPF or DKIM result passes with DMARC alignment | Inspect headers |
temperror | Temporary authentication evaluation error | Check DNS availability and retry after recovery |
SMTP handoff fails | Pronto could not submit the message to the relay | Check connection settings and sender permissions |
Compact authentication result guide
For the quickest end-to-end check, send a Pronto-generated message to the address shown by the tester. Use the same procedure, From address, and relay as production so the result covers the real configuration.
The report should show the visible From domain, Return-Path, DKIM selector, signing domain, sending IP, and DMARC result together. Save that output as the baseline for later changes.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
If authentication fails, compare the test with the Pronto component that sent it. A different workflow, sender account, or server address can make a correct DNS change appear ineffective.
Work through the failure in protocol order. SPF uses the envelope domain, DKIM uses the selector and d= domain, and DMARC compares either passing domain with the visible From domain.
- Duplicate SPF. Combine every authorized source into one SPF TXT record at each hostname.
- Too many lookups. Remove obsolete SPF mechanisms and reduce nested includes when evaluation exceeds the 10-term limit and returns permerror.
- Wrong selector. Read s= and d= from DKIM-Signature, then query s._domainkey.d with those actual values.
- Body hash failure. Check whether a relay or gateway changes content after DKIM signing.
- Unexpected source. Confirm whether another Pronto procedure or deployment sends through a separate route.
Monitor Pronto authentication failures
A one-time pass can break after a relay migration, selector rotation, DNS edit, or new Pronto workflow. Keep continuous DMARC monitoring on the domain to detect source changes and authentication failures in report data.
- Track the source. Record the Pronto route's sending IP, envelope domain, DKIM domain, and rDNS in test-message headers, then compare the identifiers available in aggregate reports.
- Set failure alerts. Notify the mail owner when DMARC failures rise or a previously verified Pronto source changes identity.
- Watch DNS health. Detect a missing DKIM selector, duplicate SPF record, lookup overflow, or altered DMARC policy.
- Keep ownership clear. Route each issue to the Pronto administrator, DNS owner, or relay owner based on the failing control.
Monitor the Pronto route in Suped
Suped is our DMARC reporting and email authentication platform. Use it to review the Pronto route's reported sources and investigate authentication failures. Aggregate reports commonly arrive daily; alerts based on those reports do not confirm each message's delivery in real time.
- Correlate signals. Review authentication results with relevant blocklist (blacklist) data when investigating the Pronto sending IP.
- Detect changes. Investigate a new Pronto source or a drop in its reported DMARC pass rate, then confirm the cause with a fresh message test.
Keep the original Pronto test message and its source identity as a reference. When an alert arrives, compare the current Return-Path, d= domain, selector, and sending IP with that known-good message before changing DNS.
Choose and stage DMARC enforcement
Consider p=reject only after every legitimate Pronto route and other approved sender passes DMARC with valid DKIM signing. Use aggregate data to identify unauthorized mail before changing policy.
Check whether reject fits the domain
RFC 9989 advises against p=reject for general-purpose email domains because mailing lists and forwarding create interoperability problems. For controlled Pronto transactional mail, consider a dedicated From subdomain with its own DMARC policy.
- Inventory sources. Identify every Pronto environment, procedure, From domain, relay, and non-Pronto sender in the report data.
- Verify DKIM. Confirm each approved source has valid DKIM with DMARC alignment before reject; retain SPF authorization where supported.
- Remove uncertainty. Classify every material failure before enforcement. Do not approve an unknown source only because it sends high volume.
- Apply quarantine. Set p=quarantine after approved sources authenticate. Review a complete invoice and statement cycle for legitimate failures.
- Review impact. Investigate failures before changing policy again; one reporting cycle does not cover infrequent workflows.
- Request reject where appropriate. Change to p=reject only after the domain-use review, keep reporting enabled, and continue watching new Pronto routes or key rotations.
DMARC enforcement stages
Review approved traffic and domain use before changing the requested DMARC policy.
Monitor
p=none
Map legitimate sources
Quarantine
p=quarantine
Review legitimate impact
Reject where appropriate
p=reject
Request rejection for failures
Successive DMARC policy values, publish only oneDNS
v=DMARC1; p=none; rua=mailto:dmarc@example.com v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com v=DMARC1; p=reject; rua=mailto:dmarc@example.com
The pct tag is historic under RFC 9989. Do not rely on percentage sampling to limit enforcement impact. The examples are successive replacements, not simultaneous DNS records.
Suped's Hosted DMARC lets the policy owner manage these changes without repeated manual TXT edits. Keep reporting enabled and review authentication failures after each policy change.
Do not lower a working p=reject policy to onboard Pronto. Fix the Return-Path or DKIM signing domain, confirm a fresh test passes, and leave enforcement intact.
Pronto email authentication FAQ
Check these details when a Pronto deployment uses a different mail route or report data shows an unfamiliar source.
Pronto Xi has no universal SPF include. Follow the SMTP or cloud mail route's DNS instructions for the actual Return-Path domain. Merge TXT mechanisms into its single SPF record, or publish a supplied CNAME for a dedicated bounce subdomain instead.
Normally, no. The outbound relay or connected mail route creates the selector, supplies the DNS record, and signs the message. Pronto Xi TrueForm Neo hands the completed message to that route.
Yes. DMARC passes when DKIM passes and its d= domain has DMARC alignment with the visible From domain. Use this path when the relay cannot provide a custom Return-Path; support depends on that relay's configuration.
A Pronto-related rDNS name can indicate Pronto Software infrastructure, but rDNS alone does not prove that Pronto Xi created the message. Pronto Xi commonly uses the configured relay, so its mail can show that relay's rDNS instead. Confirm the source with the Received chain, Return-Path, DKIM d= domain, and DMARC report data.
No. Keep p=quarantine or p=reject if it already works. Correct Pronto's SPF or DKIM alignment, verify a new message, and preserve the existing enforcement level.

