Optional: Keep up to date if powermail recognize spam (TypoScript setup):
# Get an email if spam was recognized
plugin.tx_powermail.settings.setup.spamshield.email = spamreceiver@yourdomain.de
# Write to a logfile when spam was recognized
plugin.tx_powermail.settings.setup.spamshield.logfileLocation = typo3temp/logs/powermailSpam.log
Copied!
---
Optional: Remove the default captcha field by adding the following to your Page TSConfig:
Required: If you override powermail's partial Partial/Form/Page.html in your own extension, make sure to add the variable languageIso to the f:render of the Fields:
Captcha providers can be extended using the new PSR-14 events. See thomasrawiel-powermailcaptcha:extend
Extend Captcha Providers
New in version 3.2.0
CAPTCHA validation can be extended and customized via two events:
CaptchaConfigurationEvent
The CAPTCHA provider configuration is extensible via the CaptchaConfigurationEvent. New providers can be added or existing ones overridden as long as they follow the expected configuration structure defined below.
Adjust or add providers: Use this event to modify the available CAPTCHA providers or their configuration before validation is executed.
Each CAPTCHA provider is defined via a configuration array that controls how the request is built and how the response is processed. These values allow the validation logic to remain provider-agnostic.
for further information on supported language codes.
PSR-14 events
New in version 1.8.0
New in version 2.2.0
The PSR-14 event BeforeVerifyRequestEvent has been added in order to manipulate the additional request options
that are sent to the Site-Verify-URL
New in version 3.2.0
The CaptchaConfigurationEvent has been introduced to make the default CAPTCHA provider configuration extensible, allowing listeners to adjust or extend provider-specific settings (e.g. endpoints, parameter names, request methods) before they are applied.
New in version 3.2.0
The ExpectedResponseEvent has been introduced to map provider-specific response formats to a unified boolean outcome, ensuring consistent validation handling across different CAPTCHA methods.