TYPO3 Core

Is this the "report" you are missing @Felix Nagel?

// Only add the environment status report if not in CLI mode
if (!Environment::isCli()) {
    $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['reports']['tx_reports']['status']['providers']['system'][] = EnvironmentStatusReport::class;
}

Not sure. Where is this code snippet from? I'm talking about the TYPO3\CMS\Reports\Task\SystemStatusUpdateTask class. The whole thing. The email is empty when triggered via cron and not the module UI.

CLI:

This report contains all System Status Notifications from your TYPO3 installation. Please check the status report for more information.

Site: Domain.com

Issues:

This email was sent by Domain.com from URL: 

UI:

Dieser Bericht umfasst alle Systemstatusbenachrichtungen Ihrer TYPO3-Installation. Bitte prüfen Sie den Statusbericht für mehr Informationen.

Seite: Domain.com

Probleme:
[OK]   Systemumgebungsüberprüfung             - 48 Test(s)
### Current directory (./) is within PHP include path.: 0
### File uploads allowed in PHP: 0
### Maximum post upload size correlates with maximum upload file size in PHP: 0
### PHP Memory limit is equal to or more than 128MB: 0
### PHP version is fine: 0
### Maximum PHP script execution time is equal to or more than 240: 0
### No disabled PHP functions: 0
### PHP doc_root is not set: 0
### PHP open_basedir is off: 0
### PHP xdebug extension not loaded: 0
### PHP max_input_vars ok: 0
### PHP Doc comment reflection works: 0
### Apache ThreadStackSize is not an issue on UNIX systems: 0
### PHP extension "filter" loaded: 0
### PHP extension "gd" loaded: 0
### PHP extension "hash" loaded: 0
### PHP extension "json" loaded: 0
### PHP extension "libxml" loaded: 0
### PHP extension "PDO" loaded: 0
### PHP extension "session" loaded: 0
### PHP extension "SPL" loaded: 0
### PHP extension "standard" loaded: 0
### PHP extension "xml" loaded: 0
### PHP extension "zip" loaded: 0
### PHP extension "zlib" loaded: 0
### PHP extension "fileinfo" loaded: 0
### PHP extension "intl" loaded: 0
### PHP extension "openssl" loaded: 0
### PHP extension PCRE is loaded and version is fine: 0
### PHP GD library true color works: 0
### PHP GD library has gif support: 0
### PHP GD library has jpg support: 0
### PHP GD library has png support: 0
### PHP GD library has freetype font support: 0
### Trusted hosts pattern is configured to allow current host value.: 0
### Fetching external URLs is allowed: 0
### System locale is correct: 0
### File names with UTF-8 characters can be used.: 0
### A PHP opcode cache is loaded: 0
### FreeType True Type Font DPI: 0
### PHP libxml bug not present: 0
### MySQL version is fine: 0
### No incompatible SQL modes found.: 0
### MySQL database uses utf8 or utf8mb4. All good.: 0
### MySQL server default uses utf8 or utf8mb4. All good.: 0
### PHP extension "mysqli" loaded: 0
### PHP mysqli.reconnect is fine: 0
### PHP extension "pdo_mysql" loaded: 0

This email was sent by Domain.com from URL: https://www.domain.com/

Another issue I just noticed: its only localized when using the UI, but I guess that makes sense. When called via cron, there is no language to choose but the default language.

The problem seems to be that

{normalizedParams.siteUrl}

<f:uri.external uri="{typo3.sitename}" defaultScheme="https" />

The config I referred to is in the ext:report

There are several problems:

1) About the URL missing in the footer: is not only in the status report, but in any case where FluidEmail is used with the SystemEmail layout (for example in EXT:linkvalidator, PasswordRest etc.).

See

core/Resources/Private/Layouts/SystemEmail.html
core/Resources/Private/Layouts/SystemEmail.txt
core/Classes/Mail/FluidEmail

2) specific to the report (in EXT:report): the content is missing.

TYPO3\CMS\Reports\Task\SystemStatusUpdateTask
....

Creating the status report itself probably does not work in cli context. Using FlashMessageQueue is not a good sign.

3) May not make sense to set the sitename ({typo3.sitename}) and / or the URL ({normalizedParams.siteUrl}) in all cases, especially in a multiple site installation. (I don't think this is a big problem, since it is a system notification and it is better to have at least one URL than none at all to determine the origin, in case this does actually get sent to the wrong person

4) No clear information if SystemEmail is in fact @internal, so extensions may use this as well, which makes it more complicated to change things.