A third of Marketo users have a broken SPF record... (Part II: 'include' and DNS limits)
The continuing story of people breaking their SPF records when they shouldn’t have touched them at all for Marketo. →
A third of Marketo users have a broken SPF record. How's yours? (Part I)
It’s incredibly easy to have a broken SPF record (equivalent to not having an SPF record at all) without knowing it, because few people do exhaustive tests. →
Stop tracking mailto: links (if you want them to work)
There are great reasons to use mailto: links in marketing emails — and just as many reasons to make them actually work when they're clicked. Unfortunately, most Marketo users →
Big brands, bad code, Part 1 of ∞: A bad URL parser breaks Munchkin
In my Marketo consulting gigs, I've fixed Munchkin and forms issues for some huge brands. Hard to shock me at this point, but occasionally a high-traffic site is →
A shared DKIM key? Sounds legit.
Update, March 10, 2016: For newer customers, Marketo generates a unique keypair and distributes a non-shared public key. However, this post is relevant for the majority of Marketo users. I →
Your embedded Marketo forms are about to break in Firefox. Here's a fix.
Marketo user ED and I independently discovered (see this post [https://nation.marketo.com/message/121431]) that once Firefox DE upgraded to v46, embedded forms would no longer submit. It →
"It wasn't broken until you fixed it": When SPF is so wrong, it's right
Modern (or maybe I mean young!) DNS admins don’t understand SPF as well as you might think. Another reason to not give them DNS tasks unless you’ve really proven the need. →
Your Marketo SPF entry doesn't matter (unless you're paying extra)
A pervasive Marketo myth is that you must have SPF and DKIM set up for your From: domains. Truth is you only need DKIM and never need SPF for your From: domain. (If — and only if — you have a custom envelope domain, you‘ll want SPF for that.) →