- SignalDesk2 hr ago
Original Summary
I run a multi-tenant SaaS application called Ji4, which uses Resend for transactional emails, primarily ticket acknowledgements, notifications and replies. Over the past week, we've had our entire Resend account suspended twice. What happened? Malicious users signed up, created fake workspaces impersonating legitimate companies and exploited the ticketing functionality to send fraudulent emails. Fair enough, that's abuse, and we absolutely have a responsibility to prevent it. We removed the offending tenants, tightened security and got our account reinstated after the first incident. A few days later, it happened again. Another suspension. Every legitimate tenant on our platform lost email functionality. Here's what really frustrates me: No proactive notification that the service had been suspended. We discovered it because our application stopped sending emails. All legitimate customers were affected because of the actions of a handful of malicious signups. Getting reinstated involved repeated back and forth emails, explaining the architecture, our security changes and how our ticketing system works. Even after disabling registrations, introducing manual workspace approval, restricting signups to verified business addresses and blocking personal email domains, we're still going back and forth trying to get service restored. I completely understand that email providers need to protect their infrastructure and reputation. Nobody wants spam or phishing going out through their service. But surely there's a better way to handle this for paying SaaS customers? A warning, proactive notification, tenant-level isolation, temporary restrictions, something other than switching off the entire service without us even knowing. We've now secured the application against this abuse, but the experience has seriously damaged my confidence in Resend. If you're running a multi-tenant SaaS, I'd think carefully about making Resend a critical dependency. I'm now evaluating alternatives because I simply can't have legitimate customers losing a core feature of our application while I exchange support emails trying to get the account turned back on. Anyone else experienced this with Resend or other transactional email providers? What are people using for reliable multi-tenant SaaS email?   submitted by   /u/Own-Truth-7187 [link]   [comments]
- 情报分类:商业与市场研究
- 分类依据:内容涉及商业、投资或市场动态
- 信息来源:Reddit · SaaS
- 发布时间:2026/10/19 15:42:37
- No replies yet