TYPO3 Core

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 = noreply@yourdomain.tld # 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 = postmaster@yourdomain.tld
}

(issue imported from #M5294)