additional headers not working

I tried duplicating what you’re experiencing, and it worked fine for me; i.e., I received the BCC and got the user’s email in the reply-to when I hit “reply” for the email. I was testing it in Thunderbird. I wonder if it could be your email client? If not, possibly a conflict with another plugin?

It could be a conflict with another plugin, I guess I will need to test that one by one.

But as far as I know (which is not much), the email client cannot change the Reply-To on its own, can it?

Thanks!

I’m not sure about the plugin conflict, but I’m wondering if that might not mean that the headers weren’t actually being sent correctly.

It would be worth looking at the email source to see if they’re there and correct. Here’s how they look when they work:

Return-path: <[email protected]>
Envelope-to: [email protected]
Delivery-date: Thu, 24 Mar 2016 14:08:36 -0500
Received: from host by host.mydomain.com with local (Exim 4.86_1)
	(envelope-from <[email protected]>)
	id 1ajAcW-0005vc-5f; Thu, 24 Mar 2016 14:08:36 -0500
To: [email protected]
Subject: Test Site "Testing"
X-PHP-Script: mydomain.com/index.php for xx.xxx.xxx.xxx
Date: Thu, 24 Mar 2016 19:08:36 +0000
From: Bob Smith <[email protected]>
Message-ID: <[email protected]>
X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)
X-WPCF7-Content-Type: text/plain
Reply-To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I don’t know that the email client would change the Reply-to on its own, I was just trying to think of all the variables that would cause what you’re doing to fail when it works for me.

To: [email protected]
Subject: Novo artigo para leitura
X-PHP-Script: liberalismoeconomico.org/index.php for xx.xx.xx.xx
Date: Thu, 24 Mar 2016 14:52:18 +0000
From: Luan <[email protected]>
Message-ID: <[email protected]>
X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)
X-WPCF7-Content-Type: text/html
Reply-To: [email protected]
MIME-Version: 1.0

Do you know if this means that the plugin really sent the Reply-To header as editoracao@ ? Because if we can rule out that the email client changed it, then I need to start testing to unplug one plugin at a time.

Yes, I think that means the plugin sent the Reply-To as:

[email protected]

If it were your email client, I’d think we’d see a correct “reply-to” that wasn’t used by the email client.

I just realized, you are using the PHP mail() function to send email, and I’m using SMTP with the built-in version of PHPMailer that comes with WordPress. We could try switching you over to that if the plugin thing doesn’t pan out.

I’m using Contact Form 7, I can’t find where to choose between mail() or SMTP. Although I believe my email is also being sent through PHPMailer:

X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)

You can choose to use SMTP mail globally for WordPress, and then CF7 will do so as well. You can either set this with a plugin, like Easy WP SMTP, or my personal preference, setting it in wp-config.php, as explained in this article.

I think we’re getting off course, though. Lots of people have CF7 working without SMTP. I’d try the plugin thing first.

It’s one of my plugins. I deactivated them all and it worked. I’ll post when I find out which one it is.

Excellent! Yes, it will be interesting to see which one is doing it.

Sorry, but it’s not actually any of the plugins.

I have the email sent to my Google for Business account, which auto-forwards it to my gmail account. When I look at the source from the Google for Business one, its Reply-To is the same as To. When I look at it in my gmail, then it is the one I input for the user.

It’s interesting that gmail receives the email from the Google for Apps account, which means that it does have the information when it hits the first one. But, for some reason, Google changes it to whatever is in To.

Even more interesting perhaps is that I can’t find the user email in the source for the Google for Business email, even when I search. So it must be encrypted somehow and decrypted by gmail.

Anyways, it looks now that the plugin is fine, I’ll need to take this to Google for Business.

Thanks a lot for your help, linux4me2!!

You’re welcome. Good job finding the cause. Be sure to mark this thread as resolved so it doesn’t reflect negatively on CF7.

You are right, done.