We've identified yet another client of ours who filter all Marketo emails as follows:
Other than asking the client to whitelist our IP range (which hasn't worked with prior clients who have done this for us), is there anything we can do? We already have our SPF/DKIM setup properly, use branded tracking links, and send from our company's domain.
HI Dan,
Is this a large or small company?
In other terms, is this a feature of their in-house emailing servers or something provided by a ISP of any kind?
-Greg
Hi Greg - It's a very large, global company.
Can anyone from Marketo's email deliverability team weigh in on this?
Dan,
Please reach out through Support on this issue to have this looked at by the Deliverability Team. There are a lot of reasons for bulk folder delivery that we would need to look into.
Delivery to the bulk folder is often driven by the reputation of the individual sender. Our team would start with high level questions about how the sender is acquiring their leads and how are they maintaining their database.
-Kiersti
From the screenshot, it looks like an intermediate server/service is changing the image src. I say this because OWA does not appear to be aware that clicking to enable images will have no effect. If you could get on a machine where this is happening it would be easy to see where those URLs are being rewritten to, and presumably figure out which software is making the change.
I started to look at the source and noticed in the email header that DKIM is signed by mktosender.com. Shouldn't this be our domain?
You may see two DKIM signatures. One is your domain and the other is a Marketo domain.
If you don't see your domain also in a DKIM signature it may not be set up in the Marketo Admin console.
That particular signature indicates that you are sending from a subset of Marketo's IPs reserved for low volume, highly-vetted customers. I would definitely want to dig into these issues more keeping from a deliverability perspective.
Kiersti, see the screenshot above - those are the only DKIM signatures found in our header. And yes, we have this configured in the Admin console:
I just submitted a ticket with Support and asked them to have the Deliverability team take a look at this.
I received the following response from Support:
What the Deliverability team told me is that we are dual-signing DKIM now. Meaning that in the chance that the customer has not set up DKIM, we're signing for them anyway. Dual-signing is fine and it doesn't affect deliverability at all.
What I don't get is that we have indeed setup our DKIM - and even if this is dual-signed (and we have setup DKIM properly) - why is our domain not listed in the DKIM signature within the header?
Sanford Whiteman, does this sound right?