---
title: "Breaking: #64668 - Content Element mailform moved to legacy extension"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-64668"
source: "Changelog/7.1/Breaking-64668-MailformMovedToLegacyExtension.rst"
typo3-version: "7.1"
typo3-major: 7
type: "breaking"
issue: 64668
forge: "https://forge.typo3.org/issues/64668"
tags: ["PHP-API", "Backend", "Frontend", "LocalConfiguration", "ext:form", "TypoScript"]
rendered: "2026-09-17T21:17:42+00:00"
---

# Breaking: #64668 - Content Element mailform moved to legacy extension {#breaking-64668-content-element-mailform-moved-to-legacy-extension}

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

## Description {#description}

The fallback "mailform" functionality, containing the `FORM` ContentObject, the submission logic for sending mailform
and the content element (CType=mailform) has been moved to the legacy extension "compatibility6". This mailform
was available when the "Form" extension, introduced in TYPO3 CMS 4.7, was not installed.

The following options have been marked for deprecation:

```php
$TYPO3_CONF_VARS][FE][secureFormmail]
$TYPO3_CONF_VARS][FE][strictFormmail]
$TYPO3_CONF_VARS][FE][formmailMaxAttachmentSize]
```

The following methods within TypoScriptFrontendController have been removed:

```php
protected checkDataSubmission()
protected sendFormmail()
public extractRecipientCopy()
public codeString()
protected roundTripCryptString()
```

## Impact {#impact}

Mailform elements are missing and not rendered in the frontend anymore unless EXT:compatibility6 is loaded.

## Affected installations {#affected-installations}

Any installation using the fallback "mailform" Content Element, the FrontendDataSubmissionController or the FORM
Content Object directly will break. Additionally, any third party extension using the TypoScriptFrontendController
methods directly will stop working with a fatal error.

## Migration {#migration}

For TYPO3 CMS 7, installing EXT:compatibility6 brings back the existing functionality. For the long term the affected
installations should migrate to a different, better suited solution for sending mails and building forms.