SanfordWhiteman

This post has spurred a new series of posts on my own blog: http://blog.teknkl.com/third-marketo-users-broken-spf/

Dan, the risk comes if one of your competitors [a] uses Marketo, [b] uses the shared DKIM key, and [c] decides to get nasty. This would mean they could send email that would be indistinguishable from your (Marketo-generated) emails in every way. The emails would appear to be sent, signed and sealed...

John, I count 11 lookups in Marketo's own record, making it an unfortunate example of how the include mechanism can bite you hard. In this case it isn't you guys arbitrarily splitting your record, but you depend on other providers who have split theirs without caring how that bubbles up to the 10-lo...

Yeah, that's what I was alluding to when I mentioned the hard limitation on DNS lookups. But there isn't actually a limit on includes: since your record can only result in 10 recursive lookups across all mechanisms, that implicitly means no one mechanism can result in more than 10. If you had all i...

John, there's a not a limit of 255 characters in an SPF TXT record. There's a limit of 255 characters in a single string within a TXT record. You don't need to use includes to make longer records (in fact, since there is a hard limitation on the number of DNS lookups, having an include when you don'...

Several are private methods that aren't usable outside of the form scope. I know how to use most of the others, but there's no formal documentation other than the Forms 2.0 docs. If there's some specific thing you're trying to do, let me know.

MktoForms2.loadForm("//app-sn01.marketo.com", "466-ZFM-936", 2);MktoForms2.whenReady(function(form){form.onSuccess(function(vals,tyURL){ return false;});form.addHiddenFields({ //These are the values which are submitted to Marketo "Email": "email6@test.com", "FirstName": "Email", "LastName": ...

You should also have IT lower the TTL on your current record. While it's only 20m now, lowering it to 5m decreases the window of uncertainty and allows you to start testing that much sooner.

Classic async programming error! (I love this stuff.)The simple reason 1 doesn't work is that MktoForms2.loadForm() loads the form descriptor asynchronously. Thus the form is not going to be in the MktoForms2.allForms() array on the very next line (when the descriptor hasn't even started to be dow...

Of the 60 instances I just surveyed, 44 are using the shared key. Presumably this is because they are "legacy" clients, but since that key hasn't been revoked, there's no incentive to change and they are subject to the vulnerability discussed in my post. There are also official documents that refe...