-
Notifications
You must be signed in to change notification settings - Fork 23
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
Sendgrid BCC/CC not working correctly #34
Comments
Isn't the behavior you've described is right? Maybe share an example with expected and actual results, please? |
I am sharing the cc case. I am sending email at following For the cc email address ([email protected]), following is the details i received at gmail. I got the expected behaviour by removing the Here is the sample code used.
|
@zeeshangulzar I see. It's a design issue. Take a look:
Unfortunately, I do not have time to fix this now. I would highly appreciate a PR to fix this issue, though. |
Thanks @paveltyk I will work on it in some free time. |
Is there any work-around for this one? |
I am using Sendgrid in my Rails application, when I add emails in TO and BCC/CC, then after sending the email through my application, TO email is working fine and I got the email, but when I logged in with the same BCC/CC email in my account(e.g. Gmail), then there is no TO email details and my BCC/CC email shifted in the TO field, so that my email (that means BCC/CC email) is showing into the TO field.
As per the default process, for the BCC email user, TO email details should be in the TO field and my email (BCC email) should show into the BCC field section. But it is not working like that.
Please let me know, how can I achieve this process, so that based on the default functionality, my BCC email will display into the BCC email field instead of TO field.
Following are my config in /initialzers/mail.rb
If i remove intercept it will work as expected, but i need intercepter as I m using X-SMTPAPI' header in observer
I also tried to move my config into config/environment as mentioned here but no success.
Ruby Version: ruby 2.5.1
Rails Version: 5.1.6
The text was updated successfully, but these errors were encountered: