Bugfix/typoscript settings maillog

[weakbit]

No description provided.

[Kanti]

needs to change in ext_emconf.php aswell

[smirgol]

DRY: TemplateBasedMailMessage::getRequest(), ConfigurationUtility::getRequest(), CleanupSettingsService::createBackendRequest()

[smirgol]

One thing I'd clarify before merging: getTransport() unwraps the FileSpool, so Mailer::send() runs directly through FileSpool::send() - the mail is not logged at spool time. The log entry is only created on flush, because getRealTransport() wraps the SMTP transport again into a LoggingTransport. A mail that is spooled but not (yet) flushed (or where the flush fails) therefore never appears in the log.

IMHO the double logging does not come from the shared MailLog, but from the flush transport being wrapped again and LoggingTransport::send being called a second time. If we want to log each mail once and immediately at send time, I would reverse it: keep getTransport() wrapped (logging at spool time), no longer wrap getRealTransport() (flush without re-logging). One entry per mail, at the earliest possible point. The current approach trades this logging guarantee for more precise status information in the log. That may be intentional - but I'd like to see it documented in the PR body so it doesn't pass as an unintended behavior change.

[smirgol]

A caveat about the new spool path that should at least be documented:

Since the core fix for CVE-2026-0859, FileSpool uses a PolymorphicDeserializer with a fixed allowlist (SentMessage, RawMessage, Envelope, Address, AbstractPart, File, Headers, HeaderInterface). TemplateBasedMailMessage extends MailMessage/Email and is not included. With transport_spool_type=file, FileSpool serializes the entire TemplateBasedMailMessage; on flush, deserialization fails → the file is renamed to .invalid → the mail is neither delivered nor logged.

This is not introduced by this PR - it happens whenever the extension is used with file spool. Since LoggingDelayedTransport now explicitly adds spool support, it would be helpful to make this visible in one place (PR body or a short comment at LoggingDelayedTransport): spool in combination with the custom Email subclass currently does not work until the allowlist covers it or the extension handles it separately.

[smirgol]

Previously there was a catch for RuntimeException, now there isn't. Intended?
Also, not sure about possible in-process side-effects by setting the request globally

[smirgol]

phpunit.xml -> <env name="typo3DatabaseDriver" value="pdo_sqlite"/>?

[smirgol]

Not yet an issue, but accessing this before call to send() will except with TypeError.
How about protected ?MailLog $mailLog = null;?