-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Mailer][Sendinblue] API integration does not work anymore #48936
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
Comments
Can you investigate more and maybe propose a fix? |
I am using the Sendinblue API integration in production myself, and Please provide the actual reproducer about how you send your email.
that's totally expected. The |
Hello, I'll detail some tests here. In my tests, our
Test 1: Mailgun 1
Test 2: Sendinblue 1
Test 3: Sendinblue 2 (with replyTo)
Here is the outpur of our Messenger consumer:
Test 4: Mailgun 2 (with replyTo)
Here is the debug verbosity output of our Messenger consumer:
EML complete files are downloaded here: email_files.zip I've managed to get that the |
In your |
Can you try the same without using your custom LocaleAwareEmail (to be sure to rule out whether it is part of the issue or no) ? |
Hello @stof, Thank you for your time on this issue. I simplified my test code to drop any custom layer we had:
Results are still similar:
Do you have an idea on how I could get the final payload made to the Sendinblue endpoint? This seems to be the step to ensure if the issue is within this package (and what it might be) or if it's on Sendinblue's side. |
This is definitely weird, because my own usage of the SendinblueApiTransport has a non-empty |
Would you have an idea on how I can get the definitive payload sent to Sendinblue to ensure it contains all fields and is correctly formatted? |
I've managed to get a dump working, I think I wasn"t restarting my Messenger worker so that's why I wasn't seeing my new dumps. In
The payload seems to be correctly formed indeed. I will investigate with Sendinblue. |
Hello, the problem has been identified. Sending additional standard headers (ie Even if they don't recognize that it is a bug that sending data for an unmodifiable header can break other functionalities 🥲 I'll update my code not to define the |
If symfony/src/Symfony/Component/Mailer/Bridge/Sendinblue/Transport/SendinblueApiTransport.php Line 139 in e480a66
|
Ah, I hadn't seen this part, I will push a PR for it. |
This PR was merged into the 5.4 branch. Discussion ---------- [Mailer] add Sender to the list of bypassed headers | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #48936 | License | MIT | Doc PR | Commits ------- f50bec1 add Sender to the list of bypassed headers
Symfony version(s) affected
5.4
Description
Hello,
We realised that emails we send through the Symfony Sendinblue integration do not contain all necessary headers.
Reply-To
header is missing,To
header is empty for example.This breaks our workflow as we cannot specify a custom reply-to email address in some cases (notification that a person sent a message to one of our clients for example).
From what I see in
SendinblueApiTransport
, the whole email payload is nested in thejson
attribute of theHttpClientInterface
call.Sendinblue API reference lists all items separately : https://developers.sendinblue.com/reference/sendtransacemail
Is it possible that the integration does not send the payload correctly to Sendinblue?
Our emails sent through Mailgun do not encounter this issue, it appears only when sending through Sendinblue.
How to reproduce
symfony/sendinblue-mailer
packageReply-To
address and send itReply-To
header in the email received.Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: