suppressions
Addresses we will not send to. The `machinemail suppressions` commands: arguments, flags, examples and the API routes they call.
Addresses we will not send to. Also spelled suppression.
| Command | Summary |
|---|---|
suppressions create | Add suppression |
suppressions delete | Remove suppression |
suppressions get | Get suppression |
suppressions list | List suppressions |
Every command also takes the global flags.
suppressions create
Add suppression.
Suppress an address for the whole organization, with —reason “manual”. Adding an address that is already suppressed replaces a bounce or manual suppression (its —reason becomes manual); a complaint suppression is returned unchanged. Sends to a suppressed address return 403.
Requires the list_entry_create permission.
Flags
--email <value>string--detail <value>string--reason <value>string-d, --data <json|@file|->stringExamples
API
suppressions delete
Remove suppression.
Also: machinemail suppressions rm.
Allow sending to the address again. Organization-scoped credentials only: pod and inbox credentials get 403. Only bounce and manual suppressions can be removed: a complaint suppression returns 403 (Complaint suppressions can only be removed by MachineMail support; email support@machinemail.dev).
Requires the list_entry_delete permission.
Arguments
<email>stringRequiredExamples
API
suppressions get
Get suppression.
Requires the list_entry_read permission.
Arguments
<email>stringRequiredExamples
API
suppressions list
List suppressions.
Also: machinemail suppressions ls.
Every suppressed address in the organization (also for pod and inbox credentials). Addresses are added automatically on permanent bounces and complaints.
Requires the list_entry_read permission.
Flags
--limit <n>integer--page-token <value>string--ascendingboolean--allboolean