> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/learn-more/risk-areas/email-threats/investigate/issue-details/response-and-remediation.md).

# Response and Remediation

## Classification

Material makes classification suggestions and describes reasons to help you classify the issue. If you enable User Report Auto Classification, Material will also automatically classify and remediate based on your settings. [Learn more here](/learn-more/risk-areas/email-threats/auto-respond/user-report-auto-classification.md).

<figure><img src="/files/etSOBgByKnBgA1YBoVms" alt=""><figcaption><p>User Report Auto Classification</p></figcaption></figure>

After analyzing the analysis provided in the [issue detail view](/learn-more/risk-areas/email-threats/investigate/issue-details.md), you can also re-classify the issue as **safe, malicious**, or **spam.**

<figure><img src="/files/P6kXEg6RAvVuAhMVaign" alt="" width="182"><figcaption><p>Classification</p></figcaption></figure>

{% hint style="success" %}
Responses based on classifications trigger **after** you save your classification.
{% endhint %}

### Manual Response

Initial remediation is determined by [default settings](/learn-more/risk-areas/email-threats/auto-respond.md). Once you've analyzed the issue, if you want to update the remediation you can do that [directly in the issue detail view](/learn-more/risk-areas/email-threats/investigate/issue-details.md).

Click into any of the blocks to edit content, block type, etc. Once you save, these remediations are applied to any future issue message that's sent to a user.

<figure><img src="/files/9XGfK0BQFpkRnEQPHNGI" alt="" width="275"><figcaption><p>Response</p></figcaption></figure>

If you want to also send this response to users who received a response when the issue wasn't classified yet, check **Also send to previous reporters.**

<figure><img src="/files/BtwzAsg2hY5tjYprUvJf" alt="" width="375"><figcaption></figcaption></figure>

Learn more about [Auto-Remediation and Response, including setting defaults, here](/learn-more/risk-areas/email-threats/auto-respond.md).

{% hint style="danger" %}
Customizing the response content in the issue does not update the template that was applied by default. See [how to create a template](/learn-more/risk-areas/email-threats/auto-respond/banner-custom-message-and-template-best-practices.md#how-create-a-template) for more information.
{% endhint %}

## Block a sender

You can block a sender directly from the message details in an issue to prevent them or their associated domain from delivering messages into inboxes.

1. Begin in a specific issue.
2. In the message details, click the **Sender Address**.
3. From the quick action menu, click **Block**.

<figure><img src="/files/0WcKQ3AjGWkyK5q20dmY" alt="" width="375"><figcaption><p>Click the sender, then click Trust</p></figcaption></figure>

4. Choose to block just this sender's email address, or their entire domain:

<figure><img src="/files/XoKMXt1BfBhZkBtxCRR8" alt="" width="375"><figcaption><p>Block one sender or any sender in their domain</p></figcaption></figure>

5. A custom detection is created deleting messages from that sender. Click the pop-up in the bottom left corner to view the detection (or from Detections, search for the domain to find the detection).

<figure><img src="/files/YTANdfVeMXvYAmkTBDNx" alt="" width="230"><figcaption><p>Sender blocked successfully</p></figcaption></figure>

To unblock a sender, archive the detection.

{% hint style="warning" %}
It's possible to both Trust and Block a sender from the quick actions menu. If both actions are taken, we defer to the Trusted Entity and the sender is **not blocked,** regardless of existing or future detections.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.material.security/learn-more/risk-areas/email-threats/investigate/issue-details/response-and-remediation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.