Has anyone else experienced internal IT pushback around the MKTO domain name?

Anonymous
Not applicable

Has anyone else experienced internal IT pushback around the MKTO domain name?

Hi Everyone,

Our marketing team is having some internal issues with our IT team regarding the MKTO domain.  Everything was set-up properply, the SPF and DKIM were incorporated into our domain settings in the middle of 2012.  We successfully sent out several internal/external newsletters and programs in the second half of 2012 with no issue.

Our recent problem is that our IT team has reported our company receiving a significant increase in unsolicited emails from companies sending with the MKTO domain name beginning in January of 2013. 

So our IT team decided to quarantine all emails with the MKTO domain to reduce the amount of unsolicitied emails plaguing our executives and sales teams' inboxes. This has caused a huge issue for our marketing team.  We can no longer send emails/newsletters/tests internally because they automatically get quarentined, unless we submit service requests each time to have our IT team release individual emails.

Marketo offered to help by allowing us to submit a form for an alternative domain name, but our IT team says that that will not resolve our issue.

This whole issue isn't a huge priority for our IT team, so we haven't been able to get them to be creative and solve the issue.  So I was wondering if anyone has experienced a similar issue?  If so, how did you resolve?  Or if you just have any ideas about what we can do, that would be a big help.
Tags (1)
1 REPLY 1
Rafael_Santoni1
Level 5

Re: Has anyone else experienced internal IT pushback around the MKTO domain name?

Jordan,

Are you using an actual Marketo domain name? If you are, I suggest you do create a new sub domain of your company's domain to run in Marketo's instance. After that, you need to make sure that you incorporate best practices on your email deployments and at least try to avoid using a "from-email" that would reach your company's problem inboxes.

A good practice would be to customize your Marketo instance with something like deliver.YOUR_DOMAIN.com where of course you replace "YOUR_DOMAIN" with your company's domain name. Your IT department or whoever manages the domain name would need to create the DNS records to match what Marketo requires.

Things WILL improve.

Good luck!

Rafael