# Block a sender in Mimecast

> A Slack request adds a sender address or domain to the Mimecast blocked senders policy so active phishing stops in minutes.

Source: https://stepwork.com/marketplace/block-a-sender-in-mimecast

Automatically block a sender in Mimecast from a Slack request with Stepwork, adding the address or domain to the blocked senders policy.

**Apps:** Mimecast
**Starts with:** Slack request
**Use case:** Security response & remediation
**Best for:** Security Analyst
**Applications used:** Mimecast, Slack
**Business outcome:** Risk reduction

## Sender blocks queue behind the email admin.

When phishing is active, analysts still wait for someone with Mimecast access to add the block. Mail keeps landing while the ticket ages.

Each delay is another inbox hit. Response time depends on who is free, not on the threat.

## Active phishing senders blocked in minutes

Stepwork adds the sender address or domain to the Mimecast blocked senders policy. The run records who asked and what was blocked.

- The sender address or domain is added to the block policy.
- New mail from that sender is blocked going forward.
- If the policy change cannot be completed, the run stops.

## From Slack request to a Mimecast sender block

Security posts the sender in Slack. Stepwork adds the block in Mimecast.

1. **Request it in Slack** (Slack): A teammate posts the sender address or domain to block. That message starts the flow, and Stepwork records who asked and when.
2. **Open blocked senders** (Mimecast): Stepwork signs in to Mimecast and opens the blocked senders policy. If the console path cannot be reached, the run stops.
3. **Add the block** (Mimecast): Stepwork adds the address or domain to the policy, the same change an email admin makes during an active phishing response.
4. **Confirm and reply in Slack** (Slack): Stepwork checks that the sender is blocked, then posts the result back in Slack.

## Sender blocks stay on the response path

A deterministic agent runs the Mimecast block path you recorded. Active phishing does not wait on the next free admin.

## Questions

**Q: How do I block a Mimecast sender from Slack?**
Post the sender address or domain in Slack. Stepwork adds it to the blocked senders policy and confirms.

**Q: Can this release a message that was already held?**
That is a separate flow. Releasing a held message in Mimecast covers inbox recovery.

**Q: Does this isolate an endpoint too?**
No. Containing a host in CrowdStrike is a separate endpoint response flow.

---

This is the Markdown version of https://stepwork.com/marketplace/block-a-sender-in-mimecast, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
