[#20886] - ReplyTo in com_contact form not working
- Closed
- 27 Jun 2018
- Medium
- Build: staging
- # 20886
When a visitor fills in the contact form and the email is sent, the replyTo field is not correctly populated. So when you reply on the email, you will reply to the main site address instead of the entered email by the visitor.
Steps to reproduce the issue
Send an email with the contact form.
Expected result
When replying to an email send with the contact form it should send a reply to the email address which was entered in the form.
Actual result
The main sites email is used for replyTo instead of the entered email by the user.
Quick solution
I solved this quickly with a small change in components/com_contact/controllers/contact.php in the _sendEmail function.
I changed:
$email = JStringPunycode::emailToPunycode($data['contact_email']);
To:
$email = $data['contact_email'];
This fix works because the PHPMailer library already converts the email address to Punycode, so the com_contact component does not have to convert the email address.
joomla-cms-bot
- | Labels |
Added:
?
|
||
franz-wohlkoenig
- | Status | New | ⇒ | Information Required |
| Category | ⇒ | com_contact |
Maybe it has already been fixed in a newer version or it is because I am using SMTP? I am still using version 3.8.8, with SMTP through Amazon SES.
No - this has always worked - or we would have had millions of bug reports.
Please send the email headers
| Status | Information Required | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-06-27 11:46:10 |
| Closed_By | ⇒ | feltkamptv |
I do not see anything wrong in the headers of the email:
Received: from a9-91.smtp-out.amazonses.com ([54.240.9.91])
Date: Wed, 27 Jun 2018 11:31:05 +0000
To: support@cryptohopper.com
From: Cryptohopper <noreply@cryptohopper.com>
Reply-To: Pim Feltkamp <info@feltkamp.tv>
Subject: Cryptohopper: Without quick solution
Message-ID: <010001644102e285-1c279bf5-6b2b-4d9e-9b7a-0156f0147dfd-000000@email.amazonses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
I will close this issue now and will start investigating if the issue is with Amazon SES or our email software. But it is still strange that after implementing the mentioned solution, it started working again.
I can not confirm this - as seen from the email headers below on a test from my blog where the email address entered on the contact form submission was brian+testing@teeman.net