Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFor a Node.js app that needs a team-wide suppression list it can manage directly, Resend is the simpler documented fit: its SDK supports adding, listing and removing suppressed addresses, and its webhooks expose suppression events. Amazon SES offers comparable account-level controls and a tenant-level option for isolating suppression across customers, so it can be the better choice for AWS-centered systems or multi-tenant applications. This is an implementation comparison, not evidence that either service delivers better or costs less.
What a suppression list does for welcome emails
A transactional welcome email should not keep going to an address that has hard-bounced or generated a complaint. A suppression list records addresses that should not receive further mail under the service’s configured rules. Both Resend and Amazon SES provide suppression controls, but their scope and application-level management differ.
As an Amazon Associate I earn from qualifying purchases.
For a Node.js team, the practical choice is whether it wants a straightforward list shared across its sending domains, account- or configuration-set-level controls within SES, or isolation between individual customers in a multi-tenant application.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow Resend suppression management works
Automatic and manual entries
Resend adds addresses to suppressions for bounce (a permanent rejection), complaint (a spam report), or manual reasons. A message sent to an address on the list is skipped until the entry is removed. Resend’s documentation describes the list as team-wide: a suppressed address applies across the team’s domains and subdomains. Resend’s suppression documentation
#1 Best Overall
Node.js API operations and visibility
The documented JavaScript SDK supports adding one address with resend.suppressions.add({ email }) and adding a batch with resend.suppressions.batch.add({ emails }). A batch can contain up to 100 addresses. Teams can retrieve entries through the dashboard or API; the records include the origin and a reference to the email event that triggered an automatic suppression.
Entries can be removed by suppression ID or email, and bulk removal supports up to 100 entries at a time. Resend also documents the suppression.added and suppression.removed webhook events, as well as email.suppressed when a send matches an existing entry. These events can help application code keep an internal record aligned with provider-side changes.
Rank #2
Removing an entry does not guarantee delivery. If the address bounces again or generates another spam complaint, Resend may suppress it again.
Free tools Windows power users keep installed
One-click scans. No signup required.
How Amazon SES suppression controls work
Account-level suppression
SES account-level suppression is customer-controlled. The account setting can suppress for bounces, complaints, or both, and can be managed through the SES API v2 or console. It can also be scoped to configuration sets. When a message matches an address on the account list for a reason enabled in the setting, SES accepts the message but does not deliver it. Entries remain until removed. AWS account-level suppression documentation
Rank #3
Account-level suppressed messages still count against the daily sending quota, though they do not contribute to the reputation bounce- or complaint-rate metrics described in AWS’s guide. AWS also notes that Gmail does not provide complaint data to SES, so spam-button reports from Gmail do not populate this list.
AWS-managed global suppression
SES also maintains a global suppression list for hard bounces. It is enabled across SES accounts, but customers cannot query or directly edit it. AWS may retain a hard-bounced address there for up to 14 days. A send to an address on the global list is accepted but not delivered; the resulting Permanent / Suppressed bounce notification is the way to learn that the address was globally suppressed. Such attempts count toward both the account’s bounce rate and daily sending quota. AWS global suppression documentation
Rank #4
Tenant-level suppression for multi-tenant apps
For an application sending on behalf of multiple customers, SES tenant-level suppression can isolate suppression behavior so one tenant’s bounce or complaint does not automatically suppress another tenant’s traffic. The feature requires SES multi-tenancy, and tenant lists are Region-specific. Suppression reasons can include hard bounces, complaints, or both. Configuration-set behavior takes precedence over tenant settings, which take precedence over account defaults. AWS announced tenant-level suppression on June 1, 2026. AWS tenant suppression announcement
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Resend vs. SES for Node.js suppression lists
| Decision point | Resend | Amazon SES |
|---|---|---|
| Node.js integration | Published SDK methods for adding, batch adding, retrieving and removing suppressions. | SES API v2 and CLI management are documented; the cited sources do not establish an equivalent Node.js-specific suppression abstraction. |
| Default scope | Team-wide across domains and subdomains. | Account-level by default; tenant-level isolation is available for multi-tenant setups. |
| Suppression reasons | Automatic hard-bounce and complaint entries; manual additions are supported. | Account and tenant settings can be configured for bounces, complaints, or both; the global list covers hard bounces. |
| Inspection and events | Dashboard/API retrieval and suppression-related webhooks are documented. | Account- and tenant-level entries can be retrieved or listed through SES operations; the global list cannot be queried. |
| Operational caveat | Removing an entry does not guarantee delivery; another bounce or complaint can suppress it again. | Account-level suppressed attempts count against the daily quota. Global suppression attempts count against quota and bounce rate. |
Which service fits your welcome-email workflow?
Choose Resend for a simple team-wide workflow
Resend is a reasonable preference when application code needs direct suppression operations, visibility into provider-side changes, and one suppression policy shared across the team’s sending domains. Its published Node.js examples make those operations easy to locate in the SDK documentation.
Choose SES for AWS controls or tenant separation
SES fits teams already operating within AWS account and configuration-set controls. For a multi-tenant product, tenant-level lists add an important capability that the cited Resend documentation does not describe: isolating suppression by tenant. Account-level and tenant-level list management are customer-controlled, while the AWS global list is not queryable.
Neither set of documentation establishes a comparative deliverability result, implementation-effort measurement, or price advantage. The decision here is about documented suppression scope and management, not a provider performance ranking.
Quick Recap
How to stop sending welcome emails to bounced addresses
- Enable the provider’s suppression behavior. In Resend, hard bounces and complaints are automatically suppressed. In SES, configure account-, configuration-set-, or tenant-level reasons appropriate to the application.
- Use provider-side suppression as the sending guard. Resend skips sends to addresses on its team-wide list; SES accepts but does not deliver sends suppressed by its applicable list.
- Mirror events or inspect records where the application needs its own state. Resend documents suppression webhooks and API retrieval. SES exposes retrieval/list operations for account- and tenant-level entries; its global list is not inspectable.
- Remove an entry only when there is a sound reason. Removal does not erase the history of a bad address or ensure delivery; a renewed bounce or complaint can cause suppression again.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
