-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Mailer] Use idn encoded address otherwise Brevo throws an error #51808
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
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
Can you please add a testcase? Thank you |
@OskarStark Tests are added and fix is also contributed to the new Brevo transport. As far as I understand the test, it should not fail after doing changes to brevo or sendinblue. |
That's caused by another PR I guess. cc @StaffNowa |
@OskarStark I think it is not the same case as nullable transport. @etlam as I see your PR it is about brevo API, but why do you edit another API? Is it the same company? |
@etlam you can ignore the failing test case.
Yes, but AFAIR you had a PR regarding null transport, and this PR is failing, can you please have a look? Thanks
Yes it is! |
In 2023 Sendinblue changed its name to Brevo. |
@OskarStark I am running tests now with #51830, and we will see if it helps or not ) |
Thank you @etlam. |
We have to use the encoded email address in case of special character domains like 'kältetechnik-xyz.de' otherwise brevo fails with 400 error.