Bug #88550

EXT:form: It's not possible to set the value for reply-to dynamically

Added by Wolfgang Wagner almost 2 years ago. Updated 6 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2019-06-13
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

In the current TYPO3-Master 10.0.0-dev it is not possible to use the value for reply-to from the form input in a form.

Due to the increasingly stringent spam checks by e-mail providers, it should be possible to read the value for reply-to from the form. It should therefore be possible to use the e-mail address that a user enters in the frontend.

At the moment this does not seem to work, when sending the form an error message appears:

Swift_RfcComplianceException
Address in mailbox given [{email-1}] does not comply with RFC 2822, 3.6.2.

Attached you find a screenshot of my form configuration.


Files

2019-06-13_08-53-32.jpg (76.1 KB) 2019-06-13_08-53-32.jpg Wolfgang Wagner, 2019-06-13 08:58

Related issues

Related to TYPO3 Core - Feature #80420: Allow multiple recipients in EmailFinisherClosedMathias Brodala2017-03-23

Actions
Has duplicate TYPO3 Core - Bug #92781: Placeholders not working in multiple recipient keys/addressesClosedMathias Brodala2020-11-06

Actions
#1

Updated by Susanne Moog almost 2 years ago

  • Status changed from New to Accepted

Research:

\TYPO3\CMS\Form\Domain\Finishers\AbstractFinisher::parseOption uses $this->substituteRuntimeReferences($optionValue, $formRuntime); -> that only substitutes array values, not keys. The email addresses are an associative array where both keys and values might use placeholders.

#2

Updated by Gerrit Code Review over 1 year ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61890

#3

Updated by Christian Eßl over 1 year ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#4

Updated by Benni Mack over 1 year ago

  • Status changed from Resolved to Closed
#5

Updated by Mathias Brodala 6 months ago

  • Has duplicate Bug #92781: Placeholders not working in multiple recipient keys/addresses added
#6

Updated by Mathias Brodala 6 months ago

  • Is Regression set to Yes
#7

Updated by Mathias Brodala 6 months ago

  • Related to Feature #80420: Allow multiple recipients in EmailFinisher added

Also available in: Atom PDF