This feature request is so logical. We are evaluating MP as an agency, and this single factor is keeping us from moving forward.

Please understand: It's not about how common the issue is or isn't; it's about us providing services to our clients that we can trust and that they can trust.

No client should have to hear that email service was shut down because of what . This ultimately would look horrible on us (i.e., for choosing a platform that has such a deficiency).

We absolutely need to know that we are making a safe, sustainable, and "care-free" choice with a product. Risks like this are not acceptable, period! This is the definition of what an agency does: Act on behalf of the client in their best interests and extend their capabilities as if we were part of their own business.

Thus, this is essentially just as bad as saying if one of (MP) regular customers/users spammed, that all your customers emails go down! Really, it's no better in principle.

Please fix this asap—thank you! 👋

Good idea! I've upvoted it. Would you mind taking a look at my feature request for a Campaign tab and consider upvoting it, as well?

Thanks!

Had I known this, I wouldn't have signed up for the Agency plan.

I'll give this a couple of weeks, and if there's no movement (doesn't appear there will be), I'll adjust my MP plan.

It makes zero sense to punish the entire account. We, as agencies, have no control of what we are potentially being punished for.,

Yes, i've had all clients' mail stop for days because 1 client uploaded an older contact list without validating first. The unsub rate was minimal. But all the other clients were highly upset. It's happened a few times. and i worry that if it happens again, i'll lose clients.

Pausing the problem domain rather than all domains makes sense. Deactivate the license for the problem account, not all accounts. please.

I had to move an academic client to AWS sending because of this. Their list is totally legal and confirmed, but academic IT departments love to block emails, and professors on breaks or changing jobs, or being lazy, mess up the stats. It's not my fault, and not the client's fault. But the way MP handles this makes it my problem, even if it's not my fault.

Absolutely...! I love MP, but maybe it would even be useful when apparent bad behavior triggered a warning notification. This way we could at least investigate before having the whole account blocked.

We would really appreciate if this is implemented

Please bring this feature fast.

This policy is completely out of space, how can you block the entire account?! After all, you have an key set for each domain, block the domain, not the entire account.

I think disabling per website is fair as opposed to across all sites.