Conflicting SPF policies
Review separate SPF policies on the same domain and prepare a correction around the sending services you confirm.
EMAIL AUTHENTICATION REPAIR
Email authentication,
handled with care.
We help businesses fix verified SPF and DMARC issues, coordinate changes with their IT provider, and verify the agreed email flows.
$600 one-time.No subscription.
CHANGE PLAN / 002
ResolveCraft.ILLUSTRATIVE SAMPLE
REPAIR NOTE / 001
company.example
01
A documented finding
Two SPF policies to review.
02
A coordinated change
Confirm senders. Agree the plan.
03
A clear verification
Test the agreed email flows.
From finding to documented result.
Works with your existing IT provider
No passwords required
Scope agreed before you commit
01 / THE SERVICE
Small records.
Important details.
Email authentication settings can become inconsistent as tools change. We focus on a specific, verified issue and help move its correction forward.
SPF evaluation limits
Check how a policy is evaluated, document a verified limit issue, and agree a suitable correction for the setup.
DMARC record errors
Investigate malformed or conflicting policy records and the effect of a proposed change before it is applied.
DKIM and alignment are examined when needed to verify the email flows within the agreed scope.
02 / OUR APPROACH
A careful repair.
A clear handover.
We work with the person who manages your DNS, from the first finding to the final checks.
01CONFIRM
Understand the setup.
Confirm the issue, your active sending services, and who can apply the DNS change. Agree the scope together.
02COORDINATE
Make the change carefully.
Prepare exact instructions, preserve the previous settings, and coordinate with your designated DNS manager.
03VERIFY
Document what was tested.
Check the DNS and agreed email flows. Provide a before-and-after report and arrange a stability check at day seven.
03 / THE DELIVERABLE
You’ll know
what changed.
A clear record of the finding, the agreed correction, and the results of each test.
Useful for you. Useful for your IT provider. Explicit about anything that remains unverified.
Included in your repaircompany.example / SPF
Two separate policies.
The sample shows separate TXT records to investigate before agreeing a correction.
TXT / RECORD 01
v=spf1 include:_spf.mail.example ~allTXT / RECORD 02
v=spf1 include:_spf.app.example ~allThis finding alone does not establish whether messages are being rejected.
company.example / CHANGE PLAN
A change agreed in context.
The plan starts with confirmed senders and an authorized DNS manager.
- Confirm the services that send for this domain.
- Review the resulting policy and its evaluation.
- Save the previous settings and agree a rollback plan.
- Coordinate publication and the agreed tests.
No sender is removed simply because its configuration looks old.
company.example / VERIFICATION
Results, with their limits.
Each included flow has its own result. Untested flows remain visible.
- DNS configuration
- Checked in this example
- Primary mailbox
- Test recorded in this example
- Third-party sending service
- Test still pending in this example
- Day-seven follow-up
- To be arranged
Illustrative entries only. Authentication checks do not guarantee inbox placement.
EXAMPLE DOMAIN · NO CUSTOMER DATA
04 / A SINGLE, DEFINED SERVICE
One repair.
One clear fee.
$600
USD
one-time
one-time
No subscription. No recurring monitoring fee.
Discuss your setupEmail Authentication Repair
We confirm the scope before you commit.
- One sending domainOne primary email service
- Up to three third-party sending servicesActive services confirmed with you
- Correction plan and coordinationExact DNS instructions and a rollback plan
- Verification and a written reportDNS checks and the agreed email tests
- A day-seven stability checkArranged as part of the mission
The service covers a defined authentication repair. Complex migrations, incident response, ongoing monitoring, and reputation or content work require a different scope.
05 / GOOD QUESTIONS
A few things
worth knowing.
We already have an IT provider. Can you work with them?
Yes. We prepare the correction and coordinate with your designated DNS manager, with your permission. Your existing team or provider applies the agreed changes.
What access do you need?
We need the sending services in scope, a person authorized to approve the change, and a DNS manager who can publish it. We do not ask for your passwords. Representative test messages are sent voluntarily from the systems being checked.
Does this guarantee that emails reach the inbox?
No. We document the agreed correction and authentication checks for the flows tested. Inbox placement also depends on factors beyond authentication, including reputation and message content.
How long does a repair take?
Timing depends on the setup, DNS propagation, and the availability of your DNS manager and test messages. We agree a practical change window once the scope is confirmed.
What if our setup needs more work?
We identify work beyond the service scope before proceeding. The coordination plan, test flows, and number of correction cycles are agreed in advance. No additional service or subscription is added automatically.
LET’S TAKE A CLOSER LOOK
A specific issue.
A sensible next step.
Tell us about your domain and the systems you use to send email. We’ll start by discussing the issue and whether it fits the service.
Scope first. Commitment second.