# How to avoid email loops

<mark style="color:green;">SINCE VERSION 5.3</mark>

Email loops occur when you configure Jira Email This Issue (JETI) to send emails to an address where a mail handler is listening.

For example:

1. You receive an email.
2. JETI/Jira imports it, and stores all recipient email address (including the email address on which the handler is listening) in a custom field.
3. JETI Notifications for Issue Created/Commented event is configured to notify email addresses stored in the field.
4. When the email is processed, Jira throws the event and JETI sends out email to the address again.
5. JETI/Jira starts to import the email, and the loop starts again.

It is easy to prevent this. Choose from the following options:

* Add the Mail Handler email address to the Recipient Blocklist field in the General Configuration page of Email This Issue. No email will be sent to addresses on the blocklist. Read more [here](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/administration/general-configuration.md).
* Configure the JETI Mail Handler Context and store the mail handler email address in the Email Address Exclusion field. This will instruct the mail handler not to store the handler email address in the custom field. Read more [here](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/contexts.md).

&#x20;


---

# 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/email-this-issue-for-jira-server-data-center/faq/faq/how-to-avoid-email-loops.md?ask=<question>
```

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.