Project

General

Profile

Actions

Bug #20715

closed

no possibility to set returnpath for mails in class.t3lib_htmlmail.php

Added by Bernd Wilke almost 15 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-07-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

the existing variable $this->returnPath is used if this->forceReturnPath is set, which gets its value from $GLOBALS['TYPO3_CONF_VARS']['SYS']['forceReturnPath'].
but $this->returnPath never is initialized inside class.t3lib_htmlmail.php
only derived classes like extensions set this variable.

using the default mailform no usage of a return path is possible.

attached patch (against 4.2.8, which is not available yet in productversion selection) inserts new value to installtool ($GLOBALS['TYPO3_CONF_VARS']['SYS']['returnPath']) and uses this value in class.t3lib_htmlmail.php to initialize $this->returnPath
(issue imported from #M11472)


Files

return_path.diff (3.04 KB) return_path.diff Administrator Admin, 2009-07-04 01:36
0011472_suggestion.txt (255 Bytes) 0011472_suggestion.txt Administrator Admin, 2010-03-06 18:04
0011472_suggestion_corrected.txt (254 Bytes) 0011472_suggestion_corrected.txt Administrator Admin, 2010-05-16 22:45

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #19591: Option to set Return-Pah in e-mailClosed2008-11-11

Actions
Related to TYPO3 Core - Feature #17154: Suggesting TS configurable Return-Path, from_mail and from_name for mailformsClosed2007-03-26

Actions
Actions #1

Updated by Martin about 14 years ago

I had the problem myself and came to another solution (see attached file 0011472_suggestion.txt). Hopefully this bug will be fixed soon. Its annoying.

Actions #2

Updated by Chris topher almost 14 years ago

Send the patch to Core List!

Actions #3

Updated by Martin almost 14 years ago

@Christopher:

Why? I think creating an issue and adding comments and files to it should be the only way to organize bugfixing. I am not a t3 developer and I don't even know what the core list is.

Actions #4

Updated by Chris topher almost 14 years ago

Hi Martin,

sorry for my short comment, I thought you were another Martin who also is around here...

Well this works as follows: Bug reports are collected in this bugtracker.
When someone wrote a patch, this needs a short discussion: Some people check, if the patch does what it should and if it does not break something.
And that is done in Core List! Therefore my comment.

To get your fix integrated in the next releases of TYPO3, you should send it to Core List!
To see how that works, please check this: http://typo3.org/teams/core/core-mailinglist-rules/

Actions #5

Updated by Alexander Opitz almost 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Closed
  • Target version deleted (0)

Closed as duplicate of #17154

Actions

Also available in: Atom PDF