ping @PEtanguy

Thank you @xabbuh.

@xabbuh @nicolas-grekas Could this be also part of lower versions of symfony ? According to the email bellow the current SMTP will be terminated this month.

I will get in touch with Brevo to know exactly how long they will support the old hostname.

My answer would be that if a commercial product doesn’t care about making their user lives easier, I don’t see why we should. Anyway, I suppose we would accept a PR doing the needed changes in 6.3.

Indeed they don't care about their customers, I've done my best to have a clear answer, all we have is "that might impact the good fonction of your transactional sending".

I created a PR for 6.3 #51295

For the record :

Given that the new Brevo bridge won't be released until November (as it was merged in 6.4 and not in 6.3), I suggest merging that as a bugfix (and maybe even in the 5.4 LTS instead of having a non-working bridge as LTS)

I've merged the PR in 5.4.

@fabpot given that the previous host will stop working on August 30th, it would be great also to do a patch release (for 5.4 and 6.3) soon enough to give projects a bit of time to update this bridge before the deadline is reached so that it keeps working.

Hello, do we have a chance that a patch release will be available before August 30th ?

We make releases at the end of each month. So, the next release cycle will happen at the end of August.
But then again, I don't see why we should rush things out on our side because of a commercial company that doesn't care about their customers.

Until we tag a new release, use a dev snapshot:

"require": {
    "symfony/sendinblue-mailer": "~6.3.4@dev"
}

or switch to the new package:

"require": {
    "symfony/brevo-mailer": "^6.4@dev"
}

@derrabus switching to brevo-mailer also requires switching to framework-bundle 6.4.x-dev, otherwise the wiring won't be done.