---
title: "Breaking: #92902 - Structured Form TypoScript recipient overrides"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-92902-1788434591"
source: "Changelog/15.0/Breaking-92902-StructuredFormTypoScriptRecipientOverrides.rst"
typo3-version: "15.0"
typo3-major: 15
type: "breaking"
issue: 92902
forge: "https://forge.typo3.org/issues/92902"
tags: ["Backend", "Frontend", "ext:form", "NotScanned"]
rendered: "2026-10-07T18:53:34+00:00"
---

# Breaking: #92902 - Structured Form TypoScript recipient overrides {#breaking-92902-1788434591}

See [forge#92902](https://forge.typo3.org/issues/92902)

## Description {#description}

Form TypoScript overrides for email finisher recipient options now use structured
list entries. Email addresses are values instead of TypoScript identifiers.

## Impact {#impact}

TypoScript configurations using an email address as the key of a recipient map
are no longer supported. Recipient options configured through TypoScript replace
the complete existing list instead of being recursively merged with it.

## Affected installations {#affected-installations}

Installations using `plugin.tx_form.settings.formDefinitionOverrides`
for the `recipients`, `carbonCopyRecipients`,
`blindCarbonCopyRecipients` or `replyToRecipients`
options are affected.

## Migration {#migration}

The same migration applies to the `recipients`,
`carbonCopyRecipients`, `blindCarbonCopyRecipients` and
`replyToRecipients` options. For example, change the following
configuration:

```typoscript
recipients {
  user@example.org = User
}
```

to a structured list entry:

```typoscript
recipients {
  10 {
    email = user@example.org
    name = User
  }
}
```

The numeric key is an arbitrary list identifier. The complete desired list must
be specified because an override replaces the existing list. Dynamic TypoScript
values can be used for `email`, for example
`email.data = TSFE : fe_user|user|email`.