-
Re: New Domain? SPF and DKIM
Darrell AlfonsoAug 17, 2017 9:56 AM (in response to Dave Berry)
That's the branding domain.
Not required, but if you want to set it up so that your email links show up as link.yourcompany.com/asd;flkjadf you have to add to CNAME first.
-
Re: New Domain? SPF and DKIM
Sanford Whiteman Aug 17, 2017 7:04 PM (in response to Dave Berry)Further to Darrell's comment, the advantage of using a branding domain -- aside from cosmetic branding -- is that the mkto-*.com pattern is easily identified as a Marketo property, which makes it easier for it to appear on URI blacklists.
(Though it's very easy on a technical level to determine that link.example.com is an alias for mkto-12345.com, it's one more step that might not be taken.)
-
Re: New Domain? SPF and DKIM
Darrell AlfonsoAug 17, 2017 10:19 PM (in response to Sanford Whiteman)
Did not know that! Good point Sanford.
-
-
Re: New Domain? SPF and DKIM
Sanford Whiteman Aug 18, 2017 7:02 AM (in response to Dan Stevens.)Sure, but URIBLs just look at links first.
-
Re: New Domain? SPF and DKIM
Dan Stevens. Aug 18, 2017 7:18 AM (in response to Sanford Whiteman)Right. And btw, I was referring to "branded sender" which is different than the branding domain discussed here. Didn't mean to derail the conversation.
-
-
Re: New Domain? SPF and DKIM
Sanford Whiteman Aug 18, 2017 7:23 AM (in response to Dan Stevens.)Also... a mail client will see headers, but a browser will only see the URL. Think Outlook and Firefox w/Tracking Protection. (It's great that the mkto-*.com pattern isn't on EasyList -- doesn't meet the definition of tracking at this moment in time!)
-
-