Using contactform never sends the sender e-mail, you have to reply... that is so 1996... :-) #5977

Alex-e107nl · 2026-08-18T19:26:00Z

Alex-e107nl
Aug 18, 2026

@e107help in contact.php you find this:

			$eml = array(
				'subject'      => $subject,
				'sender_name'  => $sender_name,
				'body'         => $body,
				'replyto'      => $sender,
				'replytonames' => $sender_name,
				'template'     => 'default'
			);

But when you change it to:

			$eml = array(
				'subject'      => $subject,
				'sender_name'  => $sender_name,
				'body'         => $body . $sender,
				'replyto'      => $sender,
				'replytonames' => $sender_name,
				'template'     => 'default'
			);

The sender mail address is always in the body of the mail, or do you see another solution?

Answered by e107help[bot]

Sep 1, 2026

@rica-carv worth asking, and the trade is worth stating plainly rather than waving off.

For the recipient, nothing changes. The message goes to one person, the contact recipient the form resolves to, and that person has always had the sender's address: it rides as Reply-To on contact.php:294-301 and has done since 2021. The new row puts the same address in the body of the same message to the same reader.

Where it does differ is the case you are pointing at. Most clients drop Reply-To when a message is forwarded inline; a row in the body survives. So an address that used to stop with the recipient can now travel on to whoever they forward it to. That is the point of the change rather than …

View full answer

@Alex-e107nl · 2026-08-18T20:53:05Z

e107help[bot]
Bot Aug 18, 2026

@Alex-e107nl your reading is right: the address genuinely never reaches the message. And it isn't an oversight of the $eml array, it's decided a few lines earlier.

contact.php builds an info table onto the end of the body with the IP and, for logged-in senders, the user id and name (lines 235-243), then appends every remaining $_POST field so custom form fields come through. But line 262 unsets email_send along with the other known fields before that loop runs, so the one field the recipient most wants is the one field explicitly removed. Same reason it can't be pulled into the subject: $vars for {CONTACT_SUBJECT} is built from what is left of $_POST too.

So all the recipient has is Reply-To. That works if you hit Reply, and it is invisible in plenty of clients and gone entirely once the mail is forwarded to a colleague.

Your patch does fix it, though I'd put the address somewhere a reader will look for it rather than trailing after the closing </table>, which is where $body . $sender lands it. A row in the table that already holds the IP is a two-line change and reads properly:

$body .= "<tr><td>Email:</td><td>" . $tp->toEmail($sender, true, 'RAWTEXT') . "</td></tr>";

$sender is already check_email()d at line 196, so it is validated, but running it through toEmail() keeps it consistent with every other value in that table. The hardcoded IP: and User: labels next to it are their own small sin, so a new row probably deserves a LAN rather than adding a third one.

Separate thing you may not have spotted while you were in there: contact_emailcopy already exists as a pref, and when it is on and the sender ticks the box, they get their own copy of the message (line 307-311). Doesn't help the recipient, but it is worth knowing it's there.

Filed as #5980.

0 replies

Alex-e107nl · 2026-08-26T06:24:10Z

Alex-e107nl
Aug 26, 2026
Author

Yes, also perfect now!

<html><body>
<!--StartFragment-->Test contactformulier met captcha nieuwe versie!<br>
<br>

IP: | **.87.133.***
-- | --
E-mail adres: | service@mydomain.nl
User: | #1 Admin
gdpr: | 1


<!--EndFragment-->
</body>
</html>

THX!

2 replies

rica-carv Aug 26, 2026

Err, and if the sender don't want to disclosure his email?

e107help[bot] Bot Sep 1, 2026

@rica-carv worth asking, and the trade is worth stating plainly rather than waving off.

For the recipient, nothing changes. The message goes to one person, the contact recipient the form resolves to, and that person has always had the sender's address: it rides as Reply-To on contact.php:294-301 and has done since 2021. The new row puts the same address in the body of the same message to the same reader.

Where it does differ is the case you are pointing at. Most clients drop Reply-To when a message is forwarded inline; a row in the body survives. So an address that used to stop with the recipient can now travel on to whoever they forward it to. That is the point of the change rather than an accident of it, but it is a real widening and you are right to name it.

What has not changed is the sender's side of the bargain. Lines 220-223 refuse the submission if the address has no @ in it, so nobody can use this form without handing one over, and the body has carried their IP address since 2006 (235-238).

An anonymous contact form would be a different feature: the email field would have to become optional, and Reply-To would go with it. Core has never offered that, before this change or after.

Answer selected by Alex-e107nl

Navigation Menu

Uh oh!

Using contactform never sends the sender e-mail, you have to reply... that is so 1996... :-) #5977

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Using contactform never sends the sender e-mail, you have to reply... that is so 1996... :-) #5977

Uh oh!

Alex-e107nl Aug 18, 2026

Replies: 2 comments · 2 replies

Uh oh!

e107help[bot] Bot Aug 18, 2026

Uh oh!

Alex-e107nl Aug 26, 2026 Author

Uh oh!

rica-carv Aug 26, 2026

Uh oh!

e107help[bot] Bot Sep 1, 2026

Alex-e107nl
Aug 18, 2026

Replies: 2 comments 2 replies

e107help[bot]
Bot Aug 18, 2026

Alex-e107nl
Aug 26, 2026
Author