TYPO3 Core

Attached is a patch that solves the problem.

@Jan-Erik: It's just a backport of the 3.6 functionality, so your new feature is missing inside.

I'm working in this problem. It seems that the problems is related to earlier version of postfix. Can anybody confirm that has this problem confirm that PostFix is used as a MTA and send me which version?

@Jan-Erik: I have tried two different servers with all typo3.7.0 and Debain woody stable v3.0 release and the following postfix versions:

postfix 1.1.11-0.woody3

It didn't work on these systems. After applying the patch from Michael it works okay again.

Do you want me to try it on an unstable linux debian environment? So shall I install typo3.7.0 on an unstable version to see if the same problem with a newer postfix version number is occuring also?

Regards

Jordan van Bergen
jordanvanbergen@hotmail.com

Hi, it's me again ;-) Finally I was able to find the time to install typo3 on my unstable debian linux server. No time to test the above bug now with v3.7.0 as the standard debian install is v3.5.0. But definetely I will test v3.7.0! I'll keep you posted! Maybe next week you will have the answer if the same problem happens on an unstable version.
Regards
Jordan

I would be happy if we could solve this as soon as possible. We plan to bring out 3.7.1 at the end of next week...

Sorry, about late answer to the patch workability (due my trip to Denmark, some Typo3 work also ;-) and I came back just).
It solved the problem at least in Red Hat 7.2 - 8.0 & PostFix installations.

Yes of course because it just reverts the code back to 3.6.2 style.

Sorry, wasn't finished yet.

What I want to say is that this was just a hack but not a solution.

Jan-Erik was trying to set the return-path using the fifth parameter to PHPs mail() function.

So currently this is no longer possible but at least it's working fine everywhere...

IF we could say that it's only a specific Postfix version that causes the problem, then we can simply add a new condition that skips this feature.

BUT can we be sure it's working fine everywhere else?

Jan-Erik, did you find out anything more?

I can confirm that there is a problem with postfix 1.1 and suggest a configuration flag (in the install tool) that disables the use of the fifth parameter til sendmail (or sednmail wrapper for postfix) This way, if problems arise, just unset the parameter in the install tool, and you wont have the problem, but you will not be able to se the return.path.

Wont this work? Lets not tie it up to a version of postfix, but simply add a flag that specifies whether to use it or not like:

TYPO3_CONF_VARS['SYS']['DISABLE_EXTRAFLAGS_IN_MAIL']

Who can insert this in the install tool (if you think this is a good solution)?

As far as I can see postfix-2.XX, sendmail and exim work fine, but I havent testet too many different version.

I will try to find a fix that will work with all MTA implementations, but for now wont the configuration solve the problem?

I have installed typo3.7.0 today. Started from a clean/empty website and only inserted one page with the default mailform on the following system:

/etc/debian_version: 3.1
postfix 2.1.5-1

I entered values in the mailform and pressed SEND FORM. Immediately after this it arrived in my mailbox. So it looks like it's working on a non-woody (unstable) debian version. I assum version 3.1 stands for unstable?

I'm not sure if all dns entries in the world are already up to date but just enter something in on the following url: http://typo3bug.babeln.nl and I will let you know if I receive this. So if you ask me debian woody stable with postfix isn't working with the standard mailform and debian unstable with newer version of postfix is working okay.

Hope this helps! I found some time to test this in the little time I have. As we all do! ;-)

Regards
Jordan van Bergen
jordanvanbergen@gmail.com

Jan-Erik,
3.7.1 is on the way and we should fix this as soon as possible.

I think it has been pointed out the problem only occurs with old Postfix versions (1.x) because this version had another function for the -t switch.

My suggestion is that IF there is a way to detect Postfix + Version, then it should act automatically.
If this is not possible then I'm fine for the switch. (However I prefer the first option because there are more than enough switches already...)

Reminder. Jan-Erik, are you reading this? How should we solve the outstanding problems? Is my suggestion ok?

- michael

Jan-Erik did fix this in CVS, I will port the patch to 3.7.1.