-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BCC addresses are not added #295
Comments
BCC in email is a trick. They don't go in the email itself, only in the SMTP conversation to the server. If it went in the email, a recipient could simply look at the email header to see who it was BCC'ed to. Imagine an email being sent to
There would be no BCC header at all. The SMTP client would send three emails. One to the SMTP server for The receiving servers don't use those headers to determine who to deliver the email to. I can craft an email with headers along the lines of:
But have only you receive it; not your boss. TL; DR: Email headers are lies, and aren't used to determine what mailbox(es) an email is delivered to. |
Looks like the docs currently state the following for BCC methods:
Should we expand on that? |
It should probably be made more clear how BCC works, and that those recipients won't be in the email itself. |
Thank you. Offtopic: is there any "revolution" planned in email direction? Maybe it's time to switch to json in 2023, for example)? |
@monopolly every RFC is a "planned revolution". I have personally never submitted one myself, but I imagine that the process could start there. Good luck 👍 |
What I did:
create a email
What I expected:
email with bcc addresses
What I got:
email without bcc adresses
Release or branch I am using:
1.0.0
The problem
when you build the email in
you don't add BCC field, only CC
so the email build like this:
no BCC added
is it OK or you just forget to add BCC array to builder? Thanks
The text was updated successfully, but these errors were encountered: