TYPO3 Core

Or just when trying to send a forgotten password (felogin) to the email address of a registered user:

---
15-06-10 23:49 - cms: Locking [simple::ca454c9cb09a91b31a6b688219ea6bb5]: Acquired lock
15-06-10 23:49 - cms: $TSFE->set_no_cache() was triggered by typo3/sysext/cms/tslib/class.tslib_fe.php on line 2150. Caching is disabled!
15-06-10 23:49 - cms: $TSFE->set_no_cache() was triggered by typo3/sysext/cms/tslib/class.tslib_fe.php on line 3085. Caching is disabled!
15-06-10 23:49 - cms: Locking [simple::ca454c9cb09a91b31a6b688219ea6bb5]: Released lock
15-06-10 23:49 - Core: Mail to "" could not be sent (Subject: "Ihr neues Passwort").
---

When using the safe_mode it is allowed for mail(..) to use only four parameters (s. further below)
After changing the count of parameters to four (like below) it started to work.
---
//$success = @mail($to, $subject, $messageBody, $additionalHeaders, $additionalParameters);
$success = @mail($to, $subject, $messageBody, $additionalHeaders);
t3lib_div::debug('success1: ',$success);
---

I will switch off the safe_mode in apache.conf and try to run it with all five parameters in the call of mail(..) / t3lib/utility/class.t3lib_utility_mail.php

Meesages in the logfile:
---
16-06-10 13:34 - Core: Error handler (FE): PHP Warning: mail(): SAFE MODE Restriction in effect. The fifth parameter is disabled in SAFE MODE in /usr/share/typo3/typo3_src-4.4/t3lib/utility/class.t3lib_utility_mail.php line 80
16-06-10 13:34 - Core: Mail to "" could not be sent (Subject: "Ihr neues Passwort").

Onother issue is that you get a confirmation message even the email hasn't been sent out (in the install tool)

It works with all FIVE parameters in mail(..) / t3lib/utility/class.t3lib_utility_mail.php and switched off safe_mode (s. below the php config for apache)

---
grep safe_mode /etc/itinfra_comch/*
/etc/domain_comch/apache.conf: #php_admin_value safe_mode on
/etc/domain_comch/apache.conf: php_admin_value safe_mode off
/etc/domain_comch/apache.conf: #php_admin_value safe_mode_gid on
/etc/domain_comch/apache.conf: php_admin_value safe_mode_gid off
/etc/domain_comch/apache.conf: # php_admin_value safe_mode_include_dir /usr/share/typo3/typo3_src-4.3/
/etc/domain_comch/apache.conf: php_admin_value safe_mode_exec_dir /var/www/domain_comch/execdir/
/etc/domain_comch/domain.ch_apache-ssl.conf: #php_admin_value safe_mode on
/etc/domain_comch/domain.ch_apache-ssl.conf: php_admin_value safe_mode off
/etc/domain_comch/domain.ch_apache-ssl.conf: #php_admin_value safe_mode_gid on
/etc/domain_comch/domain.ch_apache-ssl.conf: php_admin_value safe_mode_gid off
/etc/domain_comch/domain.ch_apache-ssl.conf: php_admin_value safe_mode_exec_dir /var/www/domain_comch/execdir/
/etc/domain_comch/domain.com_apache-ssl.conf: #php_admin_value safe_mode on
/etc/domain_comch/domain.com_apache-ssl.conf: php_admin_value safe_mode off
/etc/domain_comch/domain.com_apache-ssl.conf: #php_admin_value safe_mode_gid on
/etc/domain_comch/domain.com_apache-ssl.conf: php_admin_value safe_mode_gid off
/etc/domain_comch/domain.com_apache-ssl.conf: php_admin_value safe_mode_exec_dir /var/www/domain_comch/execdir/
/etc/domain_comch/localconf.php:// If safe_mode is activated with TYPO3, disable use of
/etc/domain_comch/localconf.php_ORIG:// If safe_mode is activated with TYPO3, disable use of
/etc/domain_comch/srv1.domain4t3admin.net_apache-ssl.conf: #php_admin_value safe_mode on
/etc/domain_comch/srv1.domain4t3admin.net_apache-ssl.conf: php_admin_value safe_mode off
/etc/domain_comch/srv1.domain4t3admin.net_apache-ssl.conf: #php_admin_value safe_mode_gid on
/etc/domain_comch/srv1.domain4t3admin.net_apache-ssl.conf: php_admin_value safe_mode_gid off
/etc/domain_comch/srv1.domain4t3admin.net_apache-ssl.conf: php_admin_value safe_mode_exec_dir /var/www/domain_comch/execdir/

You can type in an email address like "xyz" and you will still get a confirmation in the install tool that a testmail has been sent to "xyz".

It is however ANOTHER issue - safe_mode (PHP) allows only 4 parameters of mail() - s. my description above.

Best regards
Mark

I guess it can be close as I didn't notice such problems with typo3 4.4.0