Skip to content
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

Universal mail not working for bcc and cc mails. #12965

Closed
ankitjain0269 opened this issue Apr 1, 2016 · 6 comments
Closed

Universal mail not working for bcc and cc mails. #12965

ankitjain0269 opened this issue Apr 1, 2016 · 6 comments

Comments

@ankitjain0269
Copy link

Universal to is not working in case of bcc and cc mail, all (to) mail goto universal mail only but it is not working in case of bcc and cc.

@GrahamCampbell
Copy link
Member

I don't understand your question. We only have code for global to and from, and nothing else.

@sebestenyb
Copy link

Hi Graham,

I understand what he mentions:

See documentation: https://laravel.com/docs/master/mail#mail-and-local-development

When developing an application that sends e-mail, you probably don't want to actually send e-mails to live e-mail addresses. Laravel provides several ways to "disable" the actual sending of e-mail messages.

Universal To

Another solution provided by Laravel is to set a universal recipient of all e-mails sent by the framework. This way, all the emails generated by your application will be sent to a specific address, instead of the address actually specified when sending the message.

I think it clearly says that all email will be sent to this Universal To set in the config, instead of the real address set.

But if you have a CC or BCC field set, then only the To field will be changed to the Universal To, the real CC or BCC recipient will still receive the email.

Probably this limitation should be mentioned in the documentation.

Cheers, Sebi

@ankitjain0269
Copy link
Author

@sebestenyb, yes this is what I was trying to say.

@makuser
Copy link

makuser commented Jan 2, 2017

@GrahamCampbell why did you close this? IMO this is a valid bugreport.

@devcircus
Copy link
Contributor

Check PR #16705. This fixed the issue.

@makuser
Copy link

makuser commented Jan 2, 2017

Wonderful. Thanks @devcircus!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants