A marketplace needs to stop sending welcome messages to invalid seller addresses without treating every delivery failure as proof that an address is invalid. Preserving the explanation takes more work than storing a bounce flag, but it makes the suppression decision reviewable. TL;DR: assess email API providers for high US deliverability by asking whether their evidence can explain and reproduce recipient suppression; use that evidence to qualify candidates before comparing delivery-rate claims.
The constraint is evidentiary: a reviewer must be able to distinguish a failed attempt, a decision to suppress, and a later decision to permit delivery. These are different records. The following design treats a suppression review as a reconstruction exercise, then derives the storage boundary and a minimal Go check from what that exercise needs.…