Hey everyone! I'm currently facing a frustrating email delivery issue because our domain is blocked by Proofpoint. Despite sending several delisting requests through their "Check IP" tool, we haven't received any responses, and it feels like nobody is reviewing our submissions at all. We've been dealing with this for several days now.
We host our services with IONOS, and other email services don't have this problem—it's just with domains protected by Proofpoint. We've also double-checked that our SPF, DKIM, and DMARC records are set up correctly, and I can assure you that our email activities are entirely legitimate and transactional.
Has anyone here had a similar experience with Proofpoint? What options do I have to resolve this without having to switch providers or change our IP addresses? I'd really appreciate any advice or insight—thanks in advance!
3 Answers
Definitely sounds like the IP reputation with IONOS is affecting you here. You might want to consider using specialized services like Amazon SES or SendGrid for your transactional emails. They tend to have better reputation management, especially if you’re facing recurring issues with Proofpoint. Just a thought!
It sounds really frustrating! One thing to keep in mind is that Proofpoint might not prioritize requests from domains that aren't their direct customers. If you can, try to get someone on the receiving end who's using Proofpoint to reach out and file a complaint—this can sometimes get their attention more effectively than your requests.
Yeah, if Proofpoint is blocking your domain, switching IPs won't solve the problem. The core issue is that Proofpoint likely isn't even considering your requests because the IP technically isn't blocked, plus those IPs probably belong to IONOS. Can IONOS file a delisting request on your behalf? Also, check your outbound mail logs for any specific rejection messages from Proofpoint—they can provide valuable insights.
We've looked at the logs, and it shows consistent rejections from their servers, but no clear reason why. I guess IONOS might have more leverage to get this resolved.