cooper-suppressions-bounces
Manage Cooper Email Bounces and Suppressions
Bounces and spam complaints can interrupt delivery and harm sender reputation. This skill guides Cooper Email investigations, rate checks, and consent-based suppression management.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "cooper-suppressions-bounces" from https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces.md and its manifest at https://skillstore.io/api/skills/cooper-email-cooper-suppressions-bounces/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « cooper-suppressions-bounces ». Cooper reports recipient_suppressed. The suppression record shows a bounce. What should I do?
Résultat attendu:
- The address is suppressed because of a bounce.
- Do not retry the same address. Ask for a corrected address.
- Remove the suppression only after confirming the address is valid and the recipient wants the mail.
Utilisation de « cooper-suppressions-bounces ». My inbox-scoped key returns permission_denied when listing Cooper suppressions.
Résultat attendu:
- Suppression listing requires an account-level key or OAuth.
- Use an authorized account connection before investigating the suppression record.
- Do not paste credentials into the conversation.
Utilisation de « cooper-suppressions-bounces ». Cooper reports recipient_blocked. Is this the same as recipient_suppressed?
Résultat attendu:
- No. A block or allow list match can return recipient_blocked.
- Suppressions are separate and can result from bounces, complaints, or manual action.
- Inspect list entries before considering policy changes. Removing a suppression does not resolve a list restriction.
Audit de sécurité
SûrAll 16 static findings are false positives involving Markdown formatting, homepage metadata, or recipient consent language. No evidence found of shell execution, reconnaissance, credential exfiltration, or prompt injection. The skill documents authenticated Cooper operations and requires confirmation of address validity and recipient consent before suppression removal.
Facteurs de risque
âïž Commandes externes (14)
đ AccĂšs rĂ©seau (1)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cooper-email-cooper-suppressions-bounces/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/cooper-email-cooper-suppressions-bounces.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
cooper-email. (2026). cooper-suppressions-bounces security audit report (audit version 1) [Author version 1]. Skillstore. https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1Citation BibTeX
@techreport{cooper-email-cooper-email-cooper-suppressions-bounces-2026,
author = {cooper-email},
title = {cooper-suppressions-bounces security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1},
note = {Author version 1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cooper-suppressions-bounces security audit report (audit version 1)"
version: "1"
type: report
authors:
- name: "cooper-email"
date-released: "2026-10-26"
url: "https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1"
identifiers:
- type: other
value: "skillstore:cooper-email-cooper-suppressions-bounces:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Resolve a suppressed recipient
Find why a customer address was suppressed and report the source message before requesting a correction or consent confirmation.
Investigate delivery trends
Review bounce and complaint rates, inspect related events, and recommend slower sending or stricter outbound controls.
Handle application delivery errors
Distinguish recipient_suppressed from recipient_blocked and identify the appropriate suppression or list management workflow.
Essayez ces prompts
Explain recipient_suppressed in Cooper Email and identify what information I need to investigate it. Do not change account settings.
Investigate why [recipient] is suppressed in Cooper Email. Summarize the reason, source message, and related events without removing the suppression.
Review Cooper Email bounce and complaint rates for the default reporting period. Summarize related events and recommend actions without changing outbound policies.
Investigate suppression and block-list status for [recipient]. Ask for confirmation of validity and consent before suppression removal; keep list policies unchanged.
Bonnes pratiques
- Inspect the suppression reason, source message, and related events before recommending action.
- Confirm address validity and recipient consent before removing a suppression.
- Monitor bounce and complaint rates, slow sending when rates rise, and review recipient lists.
Ăviter
- Retrying the same bounced address without correcting the underlying problem.
- Removing suppressions merely to bypass spam complaints or recipient consent.
- Treating suppressions and block or allow lists as the same control.
Foire aux questions
What does recipient_suppressed mean?
Which credentials can list suppressions?
When can I remove a suppression?
How should I handle a spam complaint?
How can I check bounce and complaint rates?
Does this skill install Cooper tools or configure webhooks?
Détails du développeur
Auteur
cooper-emailLicence
MIT
Version de lâauteur
v1
Révision Skillstore
r1
Avis de version
La version dĂ©clarĂ©e par lâauteur nâest pas un SemVer valide.
Réf
539af95a108e3fe7ef8081ed6fe1b45a397275d3
Récence de maintenance
26/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md