---
title: "Events"
manual: "Mail system"
version: "4.2"
permalink: "https://docs.typo3.org/permalink/mediaessenz/mail:events@4.2"
source: "Reference/Events/Index.rst"
rendered: "2026-11-03T08:21:25+00:00"
---

# Events {#events}

-   [AdditionalMailHeadersEvent](https://docs.typo3.org/permalink/mediaessenz/mail:additionalmailheadersevent@4.2)
-   [DeactivateRecipientsEvent](https://docs.typo3.org/permalink/mediaessenz/mail:deactivaterecipientsevent@4.2)
-   [ManipulateCsvImportDataEvent](https://docs.typo3.org/permalink/mediaessenz/mail:manipulatecsvimportdataevent@4.2)
-   [ManipulateMailRecipientsEvent](https://docs.typo3.org/permalink/mediaessenz/mail:manipulatemailrecipientsevent@4.2)
-   [ManipulateMarkersEvent](https://docs.typo3.org/permalink/mediaessenz/mail:manipulatemarkersevent@4.2)
-   [ManipulateRecipientEvent](https://docs.typo3.org/permalink/mediaessenz/mail:manipulaterecipientevent@4.2)
-   [RecipientsRestrictionEvent](https://docs.typo3.org/permalink/mediaessenz/mail:recipientsrestrictionevent@4.2)
-   [ScheduledSendBegunEvent](https://docs.typo3.org/permalink/mediaessenz/mail:scheduledsendbegunevent@4.2)
-   [ScheduledSendFinishedEvent](https://docs.typo3.org/permalink/mediaessenz/mail:scheduledsendfinishedevent@4.2)

## AdditionalMailHeadersEvent {#additionalmailheadersevent}

Adds possibility to modify mail headers

## DeactivateRecipientsEvent {#deactivaterecipientsevent}

To deactivate returned mail recipients within the report module (beside tt_address and fe_users), it is necessary to register corresponding event
listeners.

See `MEDIAESSENZMailEventListenerDeactivateAddresses` and `DeactivateFeUsers` for example.

> [!NOTE]
> Need an entry in a `Services.yaml` as well. It looks similar to this:
>
> ```yaml
> VENDOR\ExtensionKey\EventListener\DeactivateMyAddresses:
>   tags:
>     - name: 'event.listener'
>       identifier: 'vendor/extensionkey/deactivate-my-addresses'
> ```

## ManipulateCsvImportDataEvent {#manipulatecsvimportdataevent}

Adds possibility to modify csv data during import them to tt_address records. This needs tt_address to be installed.

## ManipulateMailRecipientsEvent {#manipulatemailrecipientsevent}

Adds possibility to manipulate the recipients list of a mailing right after finishing the mail wizard.

> [!TIP]
> Usage example (filtering out recipient duplicates):
>
> -   [https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Classes/EventListener/FilterDuplicateRecipients.php](https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Classes/EventListener/FilterDuplicateRecipients.php)
> -   [https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Services.yaml](https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Services.yaml)
>
> Attention: This example does not take into account that a duplicate recipient may have other categories.

## ManipulateMarkersEvent {#manipulatemarkersevent}

See `MEDIAESSENZMailEventListenerAddUpperCaseMarkers` for example.

> [!NOTE]
> Need an entry in a `Services.yaml` as well. For the example it looks like this:
>
> ```yaml
> MEDIAESSENZ\Mail\EventListener\AddUpperCaseMarkers:
>   tags:
>     - name: 'event.listener'
>       identifier: ''mediaessenz/mail/add-upper-case-markers'
> ```

## ManipulateRecipientEvent {#manipulaterecipientevent}

See `MEDIAESSENZMailEventListenerManipulateAddressRecipient` and `MEDIAESSENZMailEventListenerManipulateFrontendUserRecipient` for example.

> [!NOTE]
> Need an entry in a `Services.yaml` as well.

## RecipientsRestrictionEvent {#recipientsrestrictionevent}

Adds possibility to restrict recipients from extbase model sources

## ScheduledSendBegunEvent {#scheduledsendbegunevent}

Adds possibility to do something after scheduled sending begun

## ScheduledSendFinishedEvent {#scheduledsendfinishedevent}

Adds possibility to do something after scheduled sending finished

### Need more? {#need-more}

Please contact me