Bug #19243
closed
plainMailEncoded should have an additonal param for additional_parameters
Added by Chris Juerges over 16 years ago.
Updated about 11 years ago.
Description
It's no possible to set the fifth param in php mail() function.
But this is needed in Linux based server setup using postfix as mta.
The reason to use the fifth param is for example if you want to set the
Return-Path: header value. Some email provider like AOL do not like email having different From: and Return-Path: email adresses.
For postfix this param looks like this:
-rno-reply@somedomain.org
(issue imported from #M9208)
Files
Yes, this is very important, because more and more provider do some sender verification. And than this mails are often rejected.
When do we get this feature? For example notifyStageChange() uses this function. Last week I've implemented the workspace notification and was wondering why I didn't get any emails. My mail server doesn't accept emails with differnt return path. Therefore I've patched the notifyStageChange() function using the PHP mail() function. That's not nice.
Can't remember how often I stumbled about this one.
Attached patch suggests
- $GLOBALS['TYPO3_CONF_VARS']['SYS']['additionalParamForPlainMail'] (mainly for backend situations)
- TS setup config.additionalParamForPlainMail (for frontend situations only, like sending forgot passwords by fe_login - if not set and TYPO3_CONF_VARS is set, TYPO3_CONF_VARS will be used).
Both take strings like -rmy_return_path@email.com or -fmy_return_path@email.com
- Status changed from New to Needs Feedback
- Target version deleted (
0)
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
Also available in: Atom
PDF