include:mktomail.com lists the servers Adobe Marketo Engage sends from, and Adobe asks you to add it to each domain you send from. But Marketo’s return-path is “usually using a ‘*.mktomail.com’ domain”, so SPF checks Adobe’s domain and does not align with yours; Adobe recommends aligning DMARC on DKIM, or asking support for a branded return-path.
v=spf1 include:mktomail.com ~all
| Belongs to | Adobe Marketo Engage and Journey Optimizer B2B Edition |
| Needed on your domain? | The service asks for it — though by default SPF checks a different domain for its mail |
What it costs, and is it in your record?
We measure include:mktomail.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Marketo’s is there and what it costs.
What it covers
Marketo Engage email, and Journey Optimizer B2B Edition, which gives the same instruction.
Do you need it?
Adobe’s set-up asks for it: add include:mktomail.com to the SPF record of every domain you send from.
The envelope sender is Marketo’s own domain, so the include is not what makes SPF align. For that, Adobe offers a Branded Return-Path through support; otherwise DKIM carries DMARC. “Strict SPF alignment is not supported nor recommended.”
Common mistakes
- Copying it with a space after the colon — include: mktomail.com, as some Adobe pages print it — which is a syntax error.
- Trusting Marketo’s own SPF check, which cannot follow a chain of includes and shows “SPF Configuration Error” for a valid record: check with an outside SPF checker.
Sources
Checked on 26 September 2026 against these official sources:
- Set up SPF and DKIM for your Email Deliverability — experienceleague.adobe.com
- Configure Protocols for Marketo Engage — experienceleague.adobe.com
- DMARC Report Says an Email Fails SPF but the SPF Record Shows as Verified. — experienceleague.adobe.com
- “SPF Configuration Error” Notification on Redirected SPF Record — experienceleague.adobe.com