Bug #23135

mail() failed - wrong message

Added by Matthias Greiling over 10 years ago. Updated about 7 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


migrating 4.3 to 4.4 t3lib_utility_Mail::mail does not work properly.

in install tool you will be told, Mail was sent to: xxx
but it was not -
in class.t3lib_utility_mail.php sysLog() vars are not proper named,
$additionalParameters disable propper sending.
without $additionalParameters it will works.

I'm sure in 4.3 it worked fine.
Sendmail program not found or not executable? is shown
safe_mode = on

mail() works

(issue imported from #M15052)


class.t3lib_utility_mail.php (3.33 KB) class.t3lib_utility_mail.php Administrator Admin, 2010-07-08 18:22

Updated by Bernd Hanisch over 10 years ago

the problem seems, that the new function didn't check the php_safe variable. i imported the code from 4.3.3 as below:

---------row: 32 ---------------------------------------
// If safe mode is on, the fifth parameter to mail is not allowed, so the fix wont work on unix with safe_mode=On
if(!ini_get('safe_mode') && $additionalParameters) {
$success = @mail($to, $subject, $messageBody, $additionalHeaders, $additionalParameters);
} else {
$success = @mail($to, $subject, $messageBody, $additionalHeaders);


Updated by Steffen Gebert over 10 years ago

Could you have a look at the SVN history, when this was changed and maybe find a reason?

If it was forgotten, would you be so kind and send the patch as RFC to the Core list?


Updated by Alexander Opitz over 7 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No


as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?


Updated by Alexander Opitz about 7 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Also available in: Atom PDF