This post isn’t clear, are you making a statement or asking a question?
If you send a message to a group of users all of the recipients will be placed in the BCC header. They will not be able to see who else received the message.
If you’re seeing different behavior, then something is changing the headers after WordPress is done processing it.
Email Users has a “debug” mode (it is on the plugin settings page – Dashboard->Settings->Email Users). When in debug mode, Email Users will output a bunch of information including the content of the mail headers to the Dashboard but IT WILL NOT actually send the email. This allows you to see the email which is constructed without actually sending it.
Well that is the thing, i just tested it. I use the feature in a post to send this post to all users. (Notify Users About this Post)
I created a (test) subscriber and if i log in i see all the headers, including the BCC.
Screenshot
WordPress version: 3.8.1.
Email Users: 4.6.7.
I never noticed this is the previous version. Can this be a bug in the 4.6.7. version?
-Jean
What are you viewing the email with? I am not sure how an email client could view the BCC header, that seems impossible based on how the email RFC documents how headers are handled.
Marking resolved since no further information was provided.
Sorry for the late reaction. But i’ve tested this on an iPhone and webmail of iCloud.
I can test it again right now.
Just send an e-mail to a few users. I selected them with.
Screenshot select
I let one of the users send me a screenshot of the BCC, field.
Here are all the users i selected in.
Screenshot BCC field
Can this be because i’m running WP on a QNAP NAS?
I think for the SMTP there is a global SMTP relay…
Can this be the cause? Of can it be bypassed?
-Jean
Double checked my settings. I thought i found something.
Screenshot Old settings
So i deactivated the plugin and activated it again. This seems ok now.
So i ran another test. But if i send another e-mail i can still see the BCC field.
Now i also sent a test to my Gmail client.
Screenshot BCC field
I’m still checking if i can bypass the SMTP option.
-Jean
I think i found the conf that is causing this issue. It’s in the wp_mail function.
Screenshot WP_Mail setting
Because this is running on a QNAP NAS with a WordPress Installation on it think this can be not standard. I can send you my Pluggable.php version if you want?
-Jean
Extra information, i’ve compared the version of pluggable.php from the latest version.
pluggable.php
Both versions are the same. Just to be sure i’ve replaced it and did another test. Still i can see the BCC option.
So i’m out of options now. Hope you can find anything or have another idea.
Hope to hear from you.
-Jean
Fix it.
I’ve activated a plugin for SMTP.
WP Mail
Now it’s not possible to see the BCC option.
Guess the standard SMTP relay of the QNAP NAS is the issue.
The remedy is to install / activate a SMTP plugin from WordPress.
Thanks.
-Jean
What mail client are you viewing these screen shots with? Something isn’t right in your MTA as the BCC field, by definition, should never contain anything visible.
It’s not the client Mike. Screenshots are from icloud and gmail.
The SMTP relay causes the issue.
Very odd. I am not sure what you can do about that. I used the WP-Mail-SMTP plugin on an IIS based WordPress site a few years ago – that is my only experience with an SMTP plugin. It worked for me, not sure if it still works or if there is anything better.
I’m getting exactly the same problem that HiCallMeJean describes above. All the BCC addresses are visible in the messages sent out to users. Weird. How or why the BCC list should be visible in every email is a puzzle. Tried it with gmail and thunderbird, same behaviour in both. I’m using the latest version of Email Users (4.6.7) and latest wordpress (3.9.1), all running in a cpanel environment.
As a workaround, I’ve changed the Email Users setting BCC limit to ‘1: use to field’.
What is your underlying infrastructure running on? Neither Email Users nor WordPress itself can doing anything but compose valid email headers, which both do. If your mail transport isn’t honoring them correctly, I am not sure what to suggest nor how to solve it. Any address in the BCC field should never be exposed to the end client.
