Josh, if we exclude known good leads from suspension, won't this have an overall impact on our send reputation since we will continue to send to them? Or should it not impact things?
I just had the same issue - the valid email bounced with a 550 error "550 5.7.511 Access denied, banned sender". Does anyone know what this could mean?
An Exchange (incl. Office 365) server rejecting you based on the envelope sender (*@*.mktomail.com).
A matter of perspective. If a recipient server believes Marketo instances (as a whole) emit too much spam, is that wrong or right?
It's frustrating that it also happens with a dedicated IP which we spend a decent amount of money on. We've also worked really hard to get our send reputation to a great place since our newsletters are ad sponsored (and also contain great content), but our deliverability suffers because of Marketo. It seems like the only way around that would be a home-grown solution -- or is there anything else that you would recommend?
Dory, that's interesting that you're having so many issues with a dedicated IP. In fact, we were seriously considering moving to a dedicated IP given all of the deliverability issues we've been experiencing (we're on the trusted IP range that Marketo offers).
Dan, don't get me wrong, we have great deliverability overall..
But part of our business relates to sending/delivering emails, and a lot of our larger clients are also blocking Marketo emails which are product-based for the subscription part of our business.
Our % delivered looks very similar... Until we then look at the underlying data/activity logs (or running smart campaigns against these leads).
Anastasia, That is bounce is not specific enough to identify the exact cause, this could be IP or domain based. There is an escalation path with Microsoft to troubleshoot that bounce. Please create a Support case so they can troubleshoot to my team for review and escalation to Microsoft if necessary.
Manager, Privacy & Deliverability Team, Marketo, Inc.