# Using split regexp
**Use Case**
Customers frequently face the issue of having unnecessary or irrelevant content being added as a comment from a reply email to a particular issue.
An email often gets added as a comment to the issue including long threads of previous messages (e.g.: a reply email and the original event notification email to which the reply was sent).
Email This Issue supports the use of regular expressions as a way of separating the latest message from previous ones, and adding only relevant content from a reply email as a comment to the issue.
**How to solve this problem**
In this section we will show two different approaches to remove old content from reply emails, each with their own advantages and disadvantages.
**Reactive approach**
This is the classical split regex approach, which attempts to split the email body based on how various email clients format reply emails. The problem with this approach is that mail clients format reply emails differently which makes splitting difficult and prone to errors. Here are two examples of the two most widely used email clients (Gmail and MS Outlook). The red frames mark the expressions people usually try to match when wanting to use regular expressions.
**Gmail example:**
**MS Outlook email example:**
**Note:** In the above MS Outlook example the reply is sent to an email that is marked by From: Sent: To: and Subject: text.
We recommend that for multi-language purposes you try using the following regular expression in order to escape the bold formatting as well: \s\*\\\*From:|\_\_\_.|On .wrote:|----Orig.|On .(JIRA).
**Note: On cloud instances, split regex uses perl syntax, therefore it must be entered between forward slashes.**
**Note:** With this approach you don't have to modify templates, but it has many disadvantages. As it requires complex regular expressions, making it easy to mess up. It is unreliable, as the expressions depend on the mail clients, and there's a high probability of information loss.
**Proactive approach**
This approach attempts to split the email body at a well defined, previously known, unique marker.
Why we recommend using a **proactive approach** with Email This Issue:
* It is easy to use as it requires creating only one regex pattern.
* It does not depend on mail clients.
* Information loss is less probable.
* Visible markers improve customer usability.
The **proactive approach** has two small drawbacks:
* It requires the use of custom templates in which the markers can be placed.
* Due to the need of custom templates, you must implement issue notifications in Jira using Email This Issue (in case of non-service desk projects).
**Note:** We highly recommend using a proactive approach with Email This Issue.
**Step by step guide**
Using the following visible content marker will have only the latest email content above the delimiter be added as a comment.
1\. Simply add a delimiter to the top of the body in your email templates such as adding: --Please reply above this line--
2\. Add a regular expression that matches the delimiter and don’t forget to insert it between forward slashes „/”
Result: If the above settings are carried out, then the following results are to be expected. The original email is cut using a visible content marker:
Comment added to the issue, email cut above the visible content marker:
| HTML format | Wiki format |
| ----------- | ----------- |
| `` | `----` |
---
# Agent Instructions: 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:
```
GET https://docs.meta-inf.hu/email-this-issue/adding-editing-a-mail-handler/email-this-issue-for-jira-cloud-mail-handler-actions/using-split-regexp.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
