Justin_Cooperm2

It's because a bunch of HTML5 validators previously thought this wasn't valid syntax. Many have been updated to resolve it but our text editor hasn't been updated yet. I filed a ticket to fix this.

Correct, this is the behavior for both the Gmail and Outlook plugin. The emails themselves are sent by Outlook or Gmail, and as a result, tokens cannot be replaced with their values by Marketo. When you load a template in either plugin, you are just pre-filling the email with pre-written copy. Also,...

If you don't want to use a token, you can use Forms JS in an even simpler way to achieve this (either on external page or in a Marketo landing page):

SPF should be setup for any domain that you are sending email through Marketo with. You do this by adding an SPF record to your domain's DNS record. This declares to the world that the domain owner has authorized Marketo's servers to send email on behalf of this domain. If you don't set it up, it do...

Please send me an email with the functional issues you are experiencing. Again, we will not support both editors forever. We are making several improvements to the new editor and I do not want your issue to slip through the cracks. Please send me an email with a description of what's occurring that ...

That is not correct. We do proxy for these resources and external stylesheets and JS will be pulled into the editor and previewer.

That looks valid, I'm perplexed by why it wouldn't work. Minor thing is you don't need to close elements with a '/' but I don't think that would break things.

Phillip, Same thing. Can you send me direct mail at jcooperman@marketo.com with the block of code you are inserting, and what you are seeing as the result. I will look into this for you.Just FYI - I was working with another customer and realized that Dreamweaver code was being stripped/modified beca...

This isn't true, I am fixing this issue. But, there are still functional limitations (see above). It has nothing to do with security.

It's not related to security policy. Please see this thread: Using a Token in the Follow-Up URL setting of a form no longer working? We're aware of this issue and are going to be fixing this very soon. This broke because more stringent validation logic was added to the platform to avoid potential pr...