Email glossary · Practical guide
Spam complaint: a recipient signal distinct from a bounce or unsubscribe
A spam complaint reflects a recipient's unwanted-mail report or a provider's complaint signal. It is not the same event as a failed delivery or an ordinary unsubscribe request.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
These outcomes may all require review, but they describe different experiences. A complaint can occur after successful transport. An investigation should preserve the source and scope of the signal while examining audience eligibility, sender identity, offer relevance and stop handling.
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
Message accepted → recipient marks it unwanted
Transport outcome: accepted
Complaint outcome: negative recipient signal
Next review: source audience, message version and exclusion process
Do not classify the event as a network failure.Checks to make
- Validate the complaint source and affected scope.
- Honor the appropriate stop action.
- Review similar records for a systemic audience problem.
Next step and limits
Use the complaint-investigation guide to organize evidence. A low observed complaint count does not prove universal satisfaction when reporting coverage is incomplete. Avoid contacting the recipient to argue with their decision or moving them to another sending identity.
Source: Zintara product context for this operational definition
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Spam complaint investigation: trace the audience and stop repeated contact →
- Feedback loop: provider complaint reports and their coverage limits →