The SPAM Queue tab lists emails routed into the mapped SPAM queue for inspection before final classification. This queue is operationally different from the SPAM table itself: the queue holds the conversation, while the SPAM table stores sender records used for future lookup and blocking.
| Action | Visible permission name | Dependency |
|---|---|---|
| Return to Original Queue | Return to Original Queue | Requires the original queue reference to be healthy. |
| SPAM | Mark as SPAM | Requires healthy Original Queue, SPAM Queue, and SPAM Table. GenEmails writes the sender to the SPAM table first, then disconnects only if the table write succeeds. |
| SPAM Details | SPAM Details | Shows SPAM handling metadata and diagnostics for the selected conversation. |
This two-step model is deliberate. Moving an email to SPAM does not automatically blacklist the sender. Final SPAM confirmation is the stronger action because it persists the sender in the tenant's SPAM data table.