> 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/whats-new/previous-releases/1.15-to-1.43/version-1.29.md).
# Version 1.29
## Sender Search in Email Threat Issues
You can now search Email Threat Issues by sender. From the left navigation, expand **Issues** then click **Email Threats**.
Enter a sender name into the search field:
Email Threats: search by sender
***
## Issue Tab Headers
Tab headers on issues now look sharper than ever:
Updated tab headers
***
## Create Phishing Simulations from the Real Thing
You can now create phishing simulations directly from an Email Threat issue:
1. From the left navigation, expand **Issues** then click **Email Threats**.
2. Open the **issue** you want to base your simulation on.
3. Use the keyboard shortcut **cmd+k** to open the actions menu (or click **all actions** on the top right).
4. Click **Create Simulation**.
5. The simulation form preloads with a copy of the issue you selected. From here, make any changes to the email body, send dates, recipients, etc.
The simulation automatically starts on your chosen date once you add at least one recipient.
To check the simulation status and results, from the left navigation click **Simulations** then open your simulation.
{% hint style="success" %}
**Required Role**
You need to be a super admin, tenant admin, analyst, global analyst, tenant phishing simulation admin, or global phishing simulation admin to create or modify simulations.
{% endhint %}
***
## Email Threat Issues Analysis Updates
From an Email Threat [issue detail view](/getting-started/fundamentals/investigate.md#issues-page-and-issue-detail-view), phishing analysis is now divided into three, distinct sections:
* Authentication Results
* Message Signal Analysis
* User Report Auto Triage (also known as [Classification](/learn-more/risk-areas/email-threats/auto-respond/user-report-auto-classification.md)), if applicable
### Smarter Defaults
Choose whether you want more verbose explanations up front on the phishing analysis card.
From the analysis card in an Email Threat issue, click the **settings cog icon** then toggle explanation options on or off.
### Initial Classification Location
The initial classification is now included in the timeline, at the bottom of the analysis card.
***
## Group By Detection
Group {Issues} By Detection has moved on the issue view.
* To the right of search, click **Display Options:**
Display Options > Group By
***
## Detection Improvements
### Multi-Factor Authentication
* Weak factor detection is now split by factor type—more granularity, better response.
### Inbound Email Threats
#### New Detections:
* XSS (cross-site scripting) attempts in subject lines
* Procedurally generated subject gibberish
* Crypto invoice callback phishing
* TikTok impersonation
#### Updated Detections:
* Overdue invoice scam logic got smarter
* Display name spoofing now better distinguishes legit ticket systems
* Docusign and encrypted PDF performance tuned up
* Microsoft Teams impersonation logic improved
* Overlapping “To” and “CC” recipient trickery now flagged faster
* Excluded Linear’s legit links from document review URL warnings
* Various scam link and attachment rules optimized for speed and accuracy
---
# 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/whats-new/previous-releases/1.15-to-1.43/version-1.29.md?ask=&goal=
```
`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.