# Migrating legacy email settings

In March 2025, we've reworked the infrastructure behind our email alert source, enabling all common features for an email alert source too. With this, some settings have changed and were replaced by new, even more powerful features. The following will cover the steps needed to achieve the equivalent in settings when migrating from old to new.

{% hint style="info" %}
The integration email domain changed from **ilertnow\.com to** **ilertnotify.com**.
{% endhint %}

## Email filters

Conditions from the legacy email filter are defined in the same way with the alert source's [**event filter**](/alerting/configure-alerting/alert-sources.md#event-filter). Using the [ICL](broken://pages/l0DnG2KVyQN3jcBKbyXf), more fields and functions to build conditions are now available.

<figure><img src="/files/zQbxzR0EBVYIQS0VODg0" alt=""><figcaption></figcaption></figure>

## Alert grouping

For time-based and no grouping the grouping options with the same name are used. Content-based grouping can be achieved through AI-based similarity grouping, more info [here](/alerting/configure-alerting/alert-sources.md#alert-grouping).

<figure><img src="/files/uFDVfecVAgrjxEMcEo0M" alt=""><figcaption></figcaption></figure>

### Alert key extraction

Previously, only the email subject and body could be used for alert key extraction, the new [ITL](broken://pages/WvTAbPqPXVB6kdEsfoQH) based definition allows for any of the event's fields plus new functions for extracting an alert key.

<figure><img src="/files/eTklzikXotV8bXzxavO7" alt=""><figcaption></figcaption></figure>

### Alert resolution

Adding rules for resolving an alert is now done by creating a resolve alert rule. They are defined like the event filter using [ICL](broken://pages/l0DnG2KVyQN3jcBKbyXf). An improvement over the old design is the ability to create rules for not only resolving, but also creating and accepting alerts.

<figure><img src="/files/IP5kDWOywUhSvYDNwrpR" alt=""><figcaption></figcaption></figure>

## Mail log

With the new email alert source, the mail log was replaced in favor of the [alert source logs](/alerting/configure-alerting/alert-sources.md#alert-source-logs). But as before all incoming mails plus more data for each received mail is shown there, even if they did not create an alert.


---

# 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.ilert.com/integrations/inbound-integrations/email/migrating-legacy-email-settings.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.