How to set up DMARC/DKIM/SPF for FeeSynergy
Published 21 Nov 2026
Updated 21 Nov 2026
9 min read
Summarize with

To authenticate FeeSynergy email, have FeeSynergy register your sending domain, configure a custom return path for SPF, publish its supplied DKIM records, and add DMARC to your domain's DNS. Test an actual FeeSynergy message before changing DMARC enforcement. A message passes DMARC when SPF or DKIM passes with a domain that matches the visible From domain under your policy's alignment rules.
I start by requesting the account's DNS instructions. I did not find a public FeeSynergy authentication support article documenting a universal SPF include, DKIM selector, or domain-settings menu. Use the records supplied for your account; FeeSynergy's website DNS is not a configuration template for customer email.
Add your domain
I use the domain in the visible From address, such as accounts@example.com. Changing the display name or Reply-To address does not authenticate that domain.
The FeeSynergy website has separate Collect and Synergy System logins. Its public material describes automated reminders and implementation assistance. For a setup without documented self-service controls, request domain registration and verification through your FeeSynergy implementation contact or info@feesynergy.com.au.
- Identify the account. Sign in through the portal your firm uses. Give support your account identifier and the exact From address used by reminders and notifications.
- Register the domain. Ask support to add your sending domain to the account, enable custom-domain DKIM, and configure a custom return-path domain.
- Obtain DNS values. Request every record's type, complete hostname and value, plus any ownership-verification token. Ask which email workflows share this configuration.
- Verify ownership. Publish any supplied verification record at your authoritative DNS host. Ask FeeSynergy to confirm successful verification and activation after the SPF and DKIM records below resolve.

FeeSynergy's Login menu separates Collect and Synergy System access.
I keep FeeSynergy's record instructions with the change request so the DNS administrator can publish the exact values. Domain ownership verification and successful message authentication are separate checks; complete both.
Set up SPF
FeeSynergy supports return-path alignment. Ask it to use a bounce subdomain under your domain, such as bounce.example.com, and supply the required DNS records. That example hostname is illustrative, not a FeeSynergy default.
I check SPF at the domain actually used in SMTP MAIL FROM, which normally appears in the delivered message's Return-Path. SPF records do not inherit from a parent domain.
- Publish the supplied records. Add the TXT or delegated CNAME records FeeSynergy specifies for the return path. Add a bounce MX record only if its instructions require one.
- Preserve existing senders. If FeeSynergy requires editing an existing SPF TXT record at the same hostname, merge its supplied authorization into that record before the final all mechanism. Keep one SPF record per hostname.
- Check lookup limits. Keep SPF evaluation within 10 DNS-querying terms, including nested includes. Do not authorize a website IP or guess an include domain.
- Confirm the active identity. Ask FeeSynergy to activate the custom return path, then check a new delivered message. A configured bounce domain is ineffective while messages still use the provider's default domain.
Inspect the example return-path domainbash
dig +short TXT bounce.example.com dig +short CNAME bounce.example.com dig +short MX bounce.example.com
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Enter the actual return-path domain in the SPF checker. With relaxed SPF alignment, bounce.example.com and a From domain of example.com share the organizational domain. With strict alignment, the two domains must match exactly.
An SPF pass on a provider-owned return path does not give your From domain SPF alignment. DMARC still passes through valid DKIM with matching domain ownership. Keep investigating the custom return-path setup, but do not treat an SPF alignment warning alone as a DMARC failure.
Set up DKIM
I request DKIM signing for the customer's From domain, rather than relying on a signature using only FeeSynergy's domain. FeeSynergy must have the matching signing key and enable signing; a DNS entry alone cannot do that.
- Copy the supplied selectors. Publish every DKIM selector FeeSynergy provides, using its exact TXT value or CNAME target. Do not assume selectors such as default or selector1.
- Check DNS placement. Publish each selector under _domainkey at the supplied signing domain. Check whether the DNS editor appends your domain to the Host field to avoid duplicated suffixes.
- Complete activation. Ask FeeSynergy to verify the published selectors and enable custom-domain signing for the relevant reminder and notification workflows.
- Inspect a fresh message. Read d= and s= in DKIM-Signature. Confirm that the receiver reports dkim=pass for a signing domain that satisfies your DMARC alignment mode.
Look up the actual DKIM selector, replacing this examplebash
dig +short CNAME selector._domainkey.example.com dig +short TXT selector._domainkey.example.com
Relaxed DKIM alignment
For From accounts@example.com, a valid signature with d=example.com qualifies. A signing subdomain under the same organizational domain also qualifies under relaxed alignment.
Strict DKIM alignment
With adkim=s, From accounts@example.com requires d=example.com exactly. A passing signature using a different signing domain does not satisfy strict alignment.
I retain old selector records during a key rotation until FeeSynergy confirms they are no longer needed. Removing a selector while queued messages still use it breaks verification.
Set up DMARC
If your domain has no DMARC policy, start with p=none to collect reports while testing. If it already uses p=quarantine or p=reject, keep that policy and its reporting destinations while fixing FeeSynergy authentication.
Use our DMARC record generator to prepare a record. The example below is the initial monitoring policy, not a replacement for an existing enforcement policy.
- Find the policy hostname. For a visible From domain of example.com, inspect _dmarc.example.com. For a From subdomain, check its own policy and the organizational domain's policy before editing.
- Publish one policy. Create or edit a single DMARC TXT record at the chosen hostname. Do not publish an additional DMARC record alongside an existing one.
- Set a working report address. Replace dmarc@example.com with your actual aggregate-report destination. For a reporting address on another domain, complete any required external reporting authorization.
- Validate the result. Check the exact From domain below and confirm the discovered policy, syntax and report destination. Preserve existing strict alignment settings unless a reviewed policy change is intended.
Initial TXT value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
The DMARC checker validates the published policy. I also test a delivered FeeSynergy message because DNS validation cannot prove that the service signs messages or uses the intended return path.
Aggregate reports commonly arrive daily. Allow 24-48 hours after real sending traffic before investigating missing reports, then check the reporting address and receiver participation. A p=none policy requests reporting without requesting quarantine or rejection for DMARC failures.
Do not leave dmarc@example.com in production. It is an example address and will not deliver your reports to your team or Suped.
Verify and troubleshoot
I test the actual FeeSynergy workflows that send mail, including an automated reminder and any separately configured financial notification. Sending through a staff mailbox tests that mailbox's infrastructure instead.
The email tester below provides a destination address and diagnoses a message sent to it. Use an internal test contact in FeeSynergy and trigger the relevant workflow with non-sensitive test data. Send directly to the tester address so forwarding does not change the authentication result.
- Confirm the sender. Check the visible From domain and Return-Path on the delivered test. Compare them with the identities configured by FeeSynergy.
- Read receiver results. Use the receiving service's trusted Authentication-Results header. Look for spf=pass, dkim=pass and dmarc=pass, then check the domains attached to those results.
- Fix the failing identity. For SPF, check the active return path and DNS evaluation. For DKIM, check the selector, signing domain and signature result. For DMARC, check domain matching and policy discovery.
- Repeat after changes. Wait for the relevant DNS cache lifetime, send a fresh FeeSynergy test, and retain the resulting headers with your change record.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
A successful direct test should show DMARC passing through the expected SPF or DKIM identity. I require working custom-domain DKIM before enforcement because forwarding commonly disrupts SPF.
Publishing DNS changes does not alter headers on messages already sent. If a new test still fails, send FeeSynergy support the timestamp, message ID and complete headers so it can check the active sending route.
Illustrative passing headers, not FeeSynergy defaultstext
From: Accounts <accounts@example.com> Return-Path: <bounce@bounce.example.com> Authentication-Results: receiver.example; spf=pass smtp.mailfrom=bounce.example.com; dkim=pass header.d=example.com; dmarc=pass header.from=example.com
|
|
|
|---|---|---|
SPF permerror | Duplicate or limit | Repair SPF |
SPF mismatch | MAIL FROM domain | Check return path |
DKIM missing | Signing enabled | Ask FeeSynergy |
DKIM fail | Selector and key | Verify DNS |
DMARC fail | Domain matching | Fix sender identity |
Get alerted when it breaks
Suped is our DMARC reporting and email authentication platform. It combines source-level authentication results with detected issues and fix instructions, so FeeSynergy failures remain visible after the initial setup.
With aggregate reports reaching Suped, use our DMARC monitoring workflow to review FeeSynergy alongside your other authorized senders. I investigate changes by source rather than relying only on the domain's overall pass rate.
- Enable issue notifications. In Notifications, configure 'Issues detected' emails and route them to the team responsible for email authentication.
- Review source verification. Enable 'Sending sources need verification'. Confirm an unfamiliar source belongs to your FeeSynergy account before marking it as verified.
- Investigate failures. Filter Data view by source or sending IP, then open Detail view to inspect SPF and DKIM domains with the DMARC result.
- Track the repair. Compare DNS history around the failure, apply the supplied fix, and confirm success with a new FeeSynergy message and subsequent reports. Enable summary emails for continuing review.
Suped's DMARC alerts depend on incoming report data. Aggregate reporting has receiver-controlled delays, so use a direct email test for immediate checks after a DNS change.
Secure your domain with p=reject
I move to p=reject after legitimate sending workflows consistently pass with the expected domains, including valid DKIM. Check every service using your domain, not only FeeSynergy, before changing the policy.
- Inventory legitimate traffic. Use Suped's source table to verify authorized services and investigate unknown traffic. Include infrequent sends across a complete billing cycle.
- Fix authentication first. Confirm FeeSynergy custom-domain DKIM passes and the custom return path works. Test each separately configured workflow and review forwarding-related failures.
- Stage enforcement. For a domain starting at p=none, move to p=quarantine after resolving legitimate failures. Review fresh reports and delivery outcomes before moving to p=reject.
- Keep monitoring. Retain the working rua destination when changing policy. Review subdomain policies and keep issue alerts enabled after enforcement.
Suped's Hosted DMARC supports policy management and staging through the dashboard after its DNS delegation is configured. Our source diagnostics help establish which legitimate senders need repair before each policy change.
Final TXT example, retaining your real report destinationtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Readiness means authorized mail passes consistently with valid custom-domain DKIM. Unrelated unauthorized traffic should not prevent enforcement. A reject policy requests rejection of DMARC-failing mail; receivers retain control over final handling.
Frequency asked questions
Request the exact authorization and return-path DNS records for your FeeSynergy account. I do not infer a customer SPF include from FeeSynergy's website domain or its corporate mail records. Publish the supplied values at the hostname used for SMTP MAIL FROM.
Yes. A valid DKIM signature using a signing domain that satisfies your DMARC alignment rules is sufficient for a DMARC pass. An SPF alignment warning still warrants checking the custom return path, but it does not by itself mean DMARC failed.
With aspf=s, the SMTP MAIL FROM domain must exactly match the visible From domain. A bounce subdomain and its parent domain differ. Keep a reviewed strict policy intact and ensure DKIM satisfies the policy, or discuss a suitable return-path configuration with FeeSynergy.
Keep an existing p=quarantine or p=reject policy. Configure FeeSynergy's sending identities and validate an internal test before enabling production sending with your domain. Do not lower protection across the domain merely to accommodate an unverified sender.
Confirm the source with the connecting IP in a trusted Received header and its PTR record, then compare the message with a known FeeSynergy test and the account's sending configuration. I do not treat an rDNS name as proof of FeeSynergy ownership or as a reason to authorize an IP in SPF. Ask FeeSynergy to confirm unfamiliar infrastructure.

