Project

General

Profile

Actions

Feature #17154

closed

Suggesting TS configurable Return-Path, from_mail and from_name for mailforms

Added by Ralf Hettinger about 17 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2007-03-26
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

The nice and quite easy to set up mailforms offered for normal editors by TYPO3 have imo a major drawback regarding mailhandling on shared hosts: There's no easy way to set a Return-Path to force maybe important emails that have been bounced by an invalid or no given address in a mailform so they would get bounced back to some responsible person.

It might be easier to understand what I'm talking about if you have an example: Let's assume there is a (rather unexperienced or not very thoughtful) content editor who has set up plenty mailforms with a TYPO3 system that is located on a shared host. Of course, he forgot to include a required email input field - and now has gone to holidays ... or his email address got deleted but he didn't care - there are such people, you know?. And all the forms he created still have this invalid email target address.

People will of course still try to contact the company he has set up all these forms for - and will never get any reply (or hopefully when he's back from holidays...): The emails sent with these forms by TYPO3 will very probably bounce - to the shared host's mail server address since no Return-Path has been set (and not unlikely will go to /dev/null). Bad.

So after all - a nice story for you to give you more evidence what the suggested parameters (patch attached) could be useful (TS Setup) for:
config.mailformDefaults { # the From: Header, if no email input field was given
email = # Set the Name, if no name input field was given
name = Online Form Message # By default, try to set the following Return-Path header, # to avoid bounced mailform mails being lost.
returnPath =
}

(issue imported from #M5294)


Files

5294.patch (1.18 KB) 5294.patch Administrator Admin, 2007-03-26 01:14
5294_4.1.2.patch (1.1 KB) 5294_4.1.2.patch Administrator Admin, 2007-07-27 16:17
0005294_4.4trunk-rev6730.patch (1.14 KB) 0005294_4.4trunk-rev6730.patch Administrator Admin, 2010-01-16 18:58

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Feature #22447: When sending mail, use TYPO3_CONF_VAR for default from address if no other address is providedClosedJeff Segars2010-04-14

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

Actions
Related to TYPO3 Core - Bug #20715: no possibility to set returnpath for mails in class.t3lib_htmlmail.phpClosed2009-07-04

Actions
Has duplicate TYPO3 Core - Bug #16817: class.t3lib_formmail.php: Return path cannot be setClosedChris topher2006-12-29

Actions
Actions #1

Updated by Bjrn Kraus almost 17 years ago

+1 for this usefull enhancement

Actions #2

Updated by Ralf Hettinger over 16 years ago

Upload of patch against TYPO3 4.1.2.
+ Handling situation, where the TS-Template might not yet be loaded.

Actions #3

Updated by Arnd Messer over 15 years ago

Thank you for this patch! =;o)

Best!
Arnd

Actions #4

Updated by Chris topher almost 14 years ago

Hi Ralf,

I think you forgot to send this one to Core List...
Maybe you can integrate your idea in Jeff's patch for #22447 which is currently pending in Core List...

Actions #5

Updated by Ralf Hettinger almost 14 years ago

Thanks Christopher.
as from my experience it's not a good idea to hook into pending patches with other (even related) stuff. I've done that before and it wasn't a very good idea since it slows down the review process and eventually getting things done... reminder to myself ;) I should rather have a look @ #22447 and provide my review...

Actions #6

Updated by Chris topher almost 14 years ago

Well I thought about adding this the same way Jeff did it. Not changing everything he has done, but complementing it so that the different options are stringent.
But do as you please.

Actions #7

Updated by Ralf Hettinger almost 14 years ago

hmhm... #22447 has been put on hold for 4.4 anyways... let's see if we find a more stringent solution for 4.5 which would incorporate this bug report here as well.

Actions #8

Updated by Alexander Opitz almost 11 years ago

  • Category deleted (Communication)
  • 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?

Actions #9

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback for over 90 days.

Actions

Also available in: Atom PDF