You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When including a BCC array, the sendgrid-ruby client either errors if an additional to is not provided, and when an additional to is provided can intermittently cause multiple duplicate emails to be sent.
Note that a to array is present in the only entry in the personalizations array.
However if you try to send this email, you get the following error
resp=sendgrid_api.client.mail._('send').post(request_body: mail.to_json)=>#<SendGrid::Response:0x00007fc3962ca4a0 @status_code="400", @body="{\"errors\":[{\"message\":\"The to array is required for all personalization objects, and must have at least one email object with a valid email address.\",\"field\":\"personalizations.1.to\",\"help\":\"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.personalizations.to\"}]}", @headers={"server"=>["nginx"], "date"=>["Thu, 06 May 2021 21:27:40 GMT"], "content-type"=>["application/json"], "content-length"=>["288"], "connection"=>["close"], "access-control-allow-origin"=>["https://sendgrid.api-docs.io"], "access-control-allow-methods"=>["POST"], "access-control-allow-headers"=>["Authorization, Content-Type, On-behalf-of, x-sg-elas-acl"], "access-control-max-age"=>["600"], "x-no-cors-reason"=>["https://sendgrid.com/docs/Classroom/Basics/API/cors.html"], "strict-transport-security"=>["max-age=600; includeSubDomains"]}>
To work around this issue we began explicitly adding the to email to the Personalization object before adding the BCC like so
# Code from previous examplepersonalization=Personalization.new# This matches the usage in https://github.com/sendgrid/sendgrid-ruby/blob/6.3.3/examples/helpers/mail/example.rb#L21personalization.add_to(to)personalization.add_bcc(Email.new(email: '[email protected]'))mail.add_personalization(personalization)mail.to_json
We opened a support case with the SendGrid team. We were told in no uncertain terms by a support rep named Anthony that the duplicate to fields were causing multiple copies of the email to be sent from one API request.
However, in our experience we only see the issue with duplicate emails intermittently, even for identical request bodies.
When we asked about the intermittent nature of our experience we were told that support does not review code and the same "resolution" was repeated in different words blaming our code generation for the issue.
If the multiple to fields are truly the issue, it's a serious bug in the SendGrid client library that the first code example that generates a single to array in the Personalizations object is not accepted.
Technical details:
sendgrid-ruby version: 6.3.3
ruby version: 2.5
The text was updated successfully, but these errors were encountered:
Issue Summary
When including a BCC array, the
sendgrid-ruby
client either errors if an additionalto
is not provided, and when an additionalto
is provided can intermittently cause multiple duplicate emails to be sent.Steps to Reproduce the Issue
Following the kitchen sink example from https://github.com/sendgrid/sendgrid-ruby/blob/6.3.3/examples/helpers/mail/example.rb#L21
The output of
mail.to_json
(not actually JSON, but a rubyHash
)Note that a
to
array is present in the only entry in thepersonalizations
array.However if you try to send this email, you get the following error
To work around this issue we began explicitly adding the
to
email to thePersonalization
object before adding the BCC like soAnd the output of
mail.to_json
Notice there are now TWO entries in the
Personalization
array, and each one specifies ato
email.This request does succeed
The Issue
We opened a support case with the SendGrid team. We were told in no uncertain terms by a support rep named Anthony that the duplicate
to
fields were causing multiple copies of the email to be sent from one API request.However, in our experience we only see the issue with duplicate emails intermittently, even for identical request bodies.
When we asked about the intermittent nature of our experience we were told that support does not review code and the same "resolution" was repeated in different words blaming our code generation for the issue.
If the multiple
to
fields are truly the issue, it's a serious bug in the SendGrid client library that the first code example that generates a singleto
array in the Personalizations object is not accepted.Technical details:
The text was updated successfully, but these errors were encountered: