Project

General

Profile

Actions

Bug #24814

closed

Swift_RfcComplianceException is always thrown in t3lib_formmail when forceReturnPath=1 is set

Added by Steffen Gebert over 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
Start date:
2011-01-25
Due date:
% Done:

0%

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

Description

A client complained about the Swift_RfcComplianceException

Address set in PathHeader does not comply with addr-spec of RFC 2822.

Catch this Exception, which comes from the SwiftMailer and output a human-readable message,e.g.

The given address '$address' is not a valid email address.

Not critical, but I'd like to have this fixed in a .1 or .2
(issue imported from #M17314)


Files

17314.diff (820 Bytes) 17314.diff Administrator Admin, 2011-01-27 12:22

Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #25030: Different usage of $GLOBALS['TYPO3_CONF_VARS']['SYS']['forceReturnPath']Closed2011-02-14

Actions
Actions #1

Updated by Steffen Gebert over 13 years ago

I'm speaking of the standard TYPO3 mail form.

Actions #2

Updated by Ernesto Baschny over 13 years ago

This is indeed a bug. In t3lib_formmail, the ReturnPath is using the $TYPO3_CONF_VARS['SYS']['forceReturnPath'] variable as the address, while it is only a boolean (0 / 1):

if ($GLOBALS['TYPO3_CONF_VARS']['SYS']['forceReturnPath']) {
$this->returnPath = $GLOBALS['TYPO3_CONF_VARS']['SYS']['forceReturnPath'];
$this->mailMessage->setReturnPath($this->returnPath);
}

This is what throws this exception. Since forceReturnPath setting is marked as "deprecated" in 4.5, we should drop the above mentioned check (SwiftMail will add a good Return-Path anyway)

=> pending in core, thanks for reporting!

Actions #3

Updated by Curt Grimley about 13 years ago

Steffen, as I just upgraded a site to 4.5.0 I started getting this same error because my recipient email address was a comma separated list of two addresses.

I can make a new email alias to handle my problem, but it sounds like lost functionality.

(I believe the formhandler extension happily accommodates a list of addresses. But I would rather not implement that when a simple stock form would suffice.)

Does this need to be a new issue or can it get bundled in here?

Actions #4

Updated by Ernesto Baschny about 13 years ago

Curt: if your trouble doesn't come from a set "forceReturnPath=1" in your localconf.php, then this is something else. In this case, please file that as a new issue in our tracker, send a reminder to myself (Ernesto Baschny) and I can take a look. Thanks!

Actions #5

Updated by Ernesto Baschny about 13 years ago

Committed to:
- trunk rev. 10586.
- TYPO3_4-5 rev. 10585 (for 4.5.1)

Actions

Also available in: Atom PDF