We’re receiving reports from several of our clients that the Retool Email resource is no longer working. The error message states that the email resource has been disabled because it was flagged for sending spam.
Message failed: 421 Domain retool-email.com is not allowed to send: Disabled for sending spam. Please contact support to resolve.
At first we assumed this was an isolated incident, but we’ve now received the same report from three different customers in two hours, so it appears to be a broader issue.
Could someone please investigate this? This is impacting production applications that rely on transactional emails as part of their normal business workflows.
Multiple production apps are failing to send transactional emails via the built-in Retool Email resource, returning the error "421 Domain retool-email.com is not allowed to send: Disabled for sending spam."
AI Response
This matches a known, active platform incident: Retool's status page confirms an unresolved incident titled "retool-email unavailable" (opened Jul 23, 2026 22:22 UTC), with the Email Server component in a Major Outage state due to the retool-email.com domain being disabled for spam. Per that incident note, official Retool emails like user invites and password resets are unaffected — only the shared sending domain used by the Email resource is impacted. Since this is a shared-domain issue on Retool's side, the fix is being handled by Retool, and subscribing to the incident is the best way to track resolution. As an interim mitigation for critical transactional emails, routing sends through your own email provider (for example, a configured SMTP resource or an external email API rather than the internal Retool Email resource) avoids dependence on the affected retool-email.com domain.
The Community Team is testing out a new automation designed to improve resource discovery. Let us know if it's helpful by leaving a or . Or by marking this post as the "Solution"! And let us know if you have any feedback here.