Authenticate the domain your requests use
SPF and DKIM for Testimonial Requests
Once requests leave through your own email provider, mailbox providers judge them by your domain. Gmail asks every sender for SPF or DKIM, and both Gmail and Outlook.com ask bulk senders for SPF, DKIM and DMARC with the From domain aligned. The work is three DNS records and a test, but the mistakes are easy: two SPF records, a DKIM key never switched on, a From address on a different domain. The checklist catches each one.
- SPF, DKIM and DMARC for the provider you connected
- Alignment between From and the signing domain
- A header check that proves it passed
The problem, solved
Where authentication goes wrong for request emails
These are the situations teams hit after connecting their own sender. The records are your job; these fixes are what StoryProof adds.
Situation 1 of 5
We connected a provider but skipped DNS
The requests send, so it looks fine. Without DKIM for your domain, mailbox providers have little reason to trust them.
How StoryProof solves it
From Pro, requests leave through your own SendGrid, Mailgun, Mailchimp or SMTP account, which is where the DKIM key for your domain is generated.
Situation 2 of 5
Now we have two SPF records
Adding a provider by publishing a second SPF record breaks SPF for the whole domain, including your normal mail.
How StoryProof solves it
Merge every sender into one SPF record. StoryProof only needs your connected provider listed, as that is the account the requests go out through.
Situation 3 of 5
Records pass but complaints rise
Authentication proves who sent a message. It does nothing for a request that annoys someone who barely remembers you.
How StoryProof solves it
Contacts and smart lists are on every plan, so each round goes to recent customers who expect to hear from you.
Situation 4 of 5
Reminders double the volume overnight
Gmail and Outlook.com add requirements for domains sending thousands a day, and chasers count toward that total.
How StoryProof solves it
From Pro, follow-ups are spaced days apart, skip anyone who unsubscribed and stop once a testimonial arrives.
Situation 5 of 5
DNS is stuck with IT for weeks
Record changes often need someone else’s approval, and the requests you meant to send this week wait with them.
How StoryProof solves it
The collection link can be shared by hand from your own mailbox, which already carries your domain’s existing records, until the new ones are live.
Record checklist
Check the three records for your request sender
Have your provider’s DNS instructions open beside this list. Cited items come from Google and Microsoft sender guidance read on 2026-11-17.
Your ticks stay in this browser tab and are not sent anywhere.
What the big mailbox providers ask for
In StoryProof
Authenticate, then send
- 1
Get the values from your provider
Each provider publishes the SPF include and DKIM record it needs. Copy them from the provider’s domain settings, not from a generic guide.
- 2
Publish and merge
Add the DKIM record, merge the SPF include into your single SPF record, and add a DMARC record with p=none if you have none.
- 3
Turn signing on and test
Verify the domain in the provider, then send a request from StoryProof to your Gmail address and read the authentication results in Show original.
- 4
Send a small round first
Ask a short list of recent customers and watch for bounces before larger sends.
What happens next: Read the DMARC reports for a few weeks. Any sender you do not recognise using your domain needs adding to SPF or stopping.
Before you start
Where this checklist stops
Only for your own provider
These records matter when requests go through your connected provider. This page says nothing about how StoryProof’s standard sending is authenticated.
A wrong record breaks normal mail
A broken SPF record or a strict DMARC policy too early can send your invoices to spam as well. Change records with whoever manages your domain.
Authentication is not reputation
Passing all three proves the mail is yours. Complaints and bounces still decide whether it lands in the inbox.
Rules may change
Gmail and Outlook.com update their sender rules. The figures here are from their pages as read on 2026-11-17.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do I need all three records?
For a few requests a day, Gmail asks for SPF or DKIM. Setting all three is still the sensible baseline, and it is required once you send thousands a day to Gmail or Outlook.com.
Should I send requests from a subdomain?
Some teams use a subdomain such as mail.yourcompany.com to keep request reputation apart from everyday mail. It needs its own SPF and DKIM, and the From address must use it.
What does alignment mean in plain words?
The domain customers see in the From line must match, or be a subdomain of, the domain that SPF or DKIM checked. Passing checks on someone else’s domain does not count.
When can I move DMARC past p=none?
Once reports show every legitimate sender passing. Microsoft suggests moving gradually from none to quarantine to reject.
Still have a question? Ask the StoryProof team or book a demo.
Requests that authenticate as you
Connect your own provider, set your records once and let StoryProof run the asking.
Sources
- Email sender guidelines, Google (Gmail Help). Checked 2026-11-17.
- Strengthening Email Ecosystem: Outlook’s New Requirements for High-Volume Senders, Microsoft Defender for Office 365 Blog. Checked 2026-11-17.
- Set up DKIM, Google Workspace Admin Help. Checked 2026-11-17.
Last updated 2026-11-17.