Marketo Integration - steps 1-4

Marketo Setup - more info: https://docs.marketo.com/display/public/DOCS/Configure+Protocols+for+Marketo

1. Create two CNAME records.

page.gitlab.com points to gitlab.mktoweb.com

 Email Tracking Link CNAME:

email.gitlab.com points to mkto-ab130188.com

---

2. Create/Update TXT record for SPF for all sending domains

 If we don’t have an SPF record, create the following record:

 If we already have an SPF record, please add this to it:

v=spf1 mx ip4:[corpIP for GitLab include:mktomail.com ~all

include:mktomail.com

---

3. Create a DKIM record for all sending domains with Marketo’s public DKIM key (txt record)

m1._domainkey.gitlab.com with the value of:

v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDhMpZsMRd5KQxo6SkQvL3aC6Gok1fXIo

DkHK+JFUH8sa0ddgVNO/XsX8j43IwiA0792LtG4g86LmgIKyM7MZhsbWC3pZGBTpB01ROWdfAzn/dGYm+

KFw2EHI9FiZzgQ8p9h/cAM9cNHafk2EtAL6/WEQsJUH9caMBgwiiV1wi/0QIDAQAB

---

4. Add Marketo Servers to our corporate whitelist

 Here is the list of server IPs:

199.15.212.0/22

94.236.119.0/26

37.188.97.188/32

185.28.196.0/22

 Postini employs a unique technology, and asks for the first and last IPs in the given range.

199.15.212.0 - 199.15.215.255

94.236.119.0 - 94.236.119.63

185.28.196.0 - 185.28.199.255

37.188.97.188

 Some anti-spam systems use the email Return-Path field instead of the IP address for whitelisting. In

those cases, the best approach is to whitelist ‘*.mktomail.com’, as Marketo uses several mailbox

subdomains.

 Other anti-spam systems whitelist based on the From address. In these situations, be sure to include all

the sending (‘From’) domains that your Marketing group uses to communicate with leads.

---

Reassigned to @jnijhof

@jacobvosmaer

Added above in our DNS but am not aware of any spam/whitelists we are using @jacobvosmaer ?

We do not have our own spam-busting system for incoming email. (@sytses: right?) Google Apps (Gmail) has built-in spam filters but I don't think that has IP whitelists. I don't think it applies to us. If it does, it only affects test email campaigns addressed to ourselves and we will find out soon enough.

Thanks doing the CNAME + SPF + DKIM @jnijhof

@jacobvosmaer we use no anti-spam apart from Google Apps

@AshleyS you should be all set now. Please reopen if I'm wrong.

Status changed to closed

@dblessing @DouweM @rspeicher

Emails aren't being sent from Marketo. Can someone check into this?

Status changed to reopened

@jnijhof could you have a look?

@AshleyS is Marketo giving errors or are the emails just never arriving?

@jacobvosmaer They aren't arriving. I've double checked with the marketo team before re-opening the issue that they are shown as sent on their end(in MKTO). They've asked us to look into our settings. cc @dblessing

@AshleyS we changed the gitlab.com SPF record around a bit. Not a permanent solution but it is no longer invalid. Is Marketo getting through now?

@dblessing and I found one problem, we had a pages.gitlab.com CNAME instead of page.gitlab.com. That has been fixed now.

@AshleyS in order to get to the bottom of this I think we need to get @dblessing in the support ticket with Marketo.

This page in Marketo seems to indicate they have verified we've configured everything correctly.

Milestone changed to Marketing

Is there anything I can do at this point?

Nope. I figured out some weird workaround that seems to be working right now.

Status changed to closed