Are you on a Marketo Shared IP address or a dedicated one? If you are on a shared address then it is pretty much a guarantee that one of these in a day will be marked on one or more blacklists (RBL) - it happens ALOT.
We noticed exactly the same issue and I dug deep into this and this is what I found/know:
If your instance sends via a server which has been blacklisted (for recipient servers who respect and use this mechanism) it will send the emails it can and any emails which do are blocked are marked as Email Suspended = True. A blacklist block is actually a softbounce but Marketo marks and sees it as a hard bounce this is owing to the fact the it is in the system as a hardbounce code "Category 1 – spam block" (Email Suspended=true (for 24 hours)).
The Email Suspended flag that I can see does not get reset after 24 hours - and I am trying to work out if its a bug or by design (I assume the former or I am missing some data to check / know) Update: Marketo will never update this status - it is a product defect/fact of life. The engineering required to change this status is too great.
If an IP address is listed on one day, the next campaign will send from a non-listed IP where possible. Note: the where possible - it is possible that your next server selection is actually also blacklisted and you need to wait until the selection process chooses a server which is not blacklisted.
RBL - delisting is done automatically by (some) anti –spam providers and normally completed between 24 and 48 hours. During the phase of delisting, the IP address will not be used in any mail campaign by those instances hosted on the POD that utilises the range.
The following IP addresess are, from what I can see are the worst offenders:
>> Does Marketo run tests on their shared servers to ensure companies like us aren't negatively impacted by other customers...
Not that I know of no.
As of today thsi is what I know of the IP ranges in use in San Jose and London
|IP||Blacklisted||# of times||Region||RBLs|
|184.108.40.206||Yes||5||NA (San Jose)||DRMX, NoSolicitado, OSPAM, SPAMCANNIBAL, UCEPROTECTL1|
|220.127.116.11||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|18.104.22.168||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|22.214.171.124||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|126.96.36.199||Yes||4||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL, UCEPROTECTL1|
|188.8.131.52||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|184.108.40.206||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|220.127.116.11||Yes||3||NA (San Jose)||DRMX, NoSolicitado, SPAMCANNIBAL|
|18.104.22.168||Yes||2||NA (San Jose)||DRMX, NoSolicitado|
|22.214.171.124||Yes||2||NA (San Jose)||NoSolicitado, SPAMCANNIBAL|
|126.96.36.199||Yes||2||NA (San Jose)||NoSolicitado, SPAMCANNIBAL|
|188.8.131.52||Yes||4||NA (San Jose)||NoSolicitado, SPAMCANNIBAL, ZapBL|
|184.108.40.206||Yes||4||NA (San Jose)||NoSolicitado, SPAMCANNIBAL, ZapBL|
|220.127.116.11||Yes||1||NA (San Jose)||NoSolicitado|
|18.104.22.168||Yes||3||NA (San Jose)||NoSolicitado, SPAMCANNIBAL, UCEPROTECTL1|
|22.214.171.124||Yes||3||NA (San Jose)||NoSolicitado, SPAMCANNIBAL, UCEPROTECTL1|
|126.96.36.199||Yes||6||EMEA (London)||CASA CBL, CASA CBLESS, CASA CBLPLUS, NoSolicitado, SORBS SPAM, UCEPROTECTL1|
|188.8.131.52||Yes||5||EMEA (London)||CASA CBL, CASA CBLESS, CASA CBLPLUS, NoSolicitado, SORBS SPAM|
|184.108.40.206||No||0||EMEA (London) (US based)|
|220.127.116.11||Yes||3||EMEA (London)||CASA CBL, CASA CBLESS, CASA CBLPLUS|
Nice post. I don't think this piece is true, though:
During the phase of delisting, the IP address will not be used in any mail campaign by those instances hosted on the POD that utilises the range.
When recipient servers are permfailing based on a blacklist that has an aging process, Marketo doesn't disable sending from the blacklisted IP automatically, as far as I know. Getting the timing right would be all but impossible anyway.
We've had a significant drop in email open rates cut in half for exact same sender name and subject line. Been doing a lot of digging but haven't been able to pin it to anything definitive.
Just curious if you discovered anything else in your investigation?
Ari, unfortunately, no. We continue to have very poor email performance - even against our existing accounts.
we recently also had some issues with some email sent from IP 18.104.22.168, which is still blacklisted as we speak:
@ Kiersti Esparza,
Would you have any feedback on this ? Is there any policy and/or recommendation from Marketo on this ?
Marketo has us on their trusted IP range of shared addresses. When entering all five of those IP addresses, they are all blacklisted on DRMX and SPAMCANNIBAL. Does anyone know if these two spam blockers are prevalent in B2B organizations?
can you look at your recent hard bounced list and Email Bounced or Invalid Reason? Might also show some detail.