A two-minute fix for the most common Brevo SMTP failure, written after losing an hour to it.
You are setting up Send mail as in Gmail, or any SMTP client, against Brevo's relay. You paste the server, port 587, your account email as the username, and the SMTP key you just generated. Gmail answers with a bare "authentication error". It reads like a wrong password. It is almost never the password.
From Brevo's own documentation:
Depending on when your account was created, your SMTP login is either your Brevo account login email address
or an automatically generated address in the format [ID]@smtp-brevo.com. Changing your
account's login email does not change your SMTP login. You can find your current SMTP login anytime on the SMTP page.
So on newer accounts the login is something like 1234567@smtp-brevo.com, a name you never chose and
that appears nowhere in your profile. It lives on the SMTP & API → SMTP page, next to the
server and port. Read it there and copy it exactly.
The second failure with the identical error message: pasting an API key where the SMTP key belongs. They come from different pages and neither works in the other's place.
xkeysib-SMTP server : smtp-relay.brevo.com Port : 587 (STARTTLS / "TLS" in Gmail) — or 465 with SSL, or 2525 Username : the SMTP login from the SMTP page, e.g. 1234567@smtp-brevo.com Password : the SMTP key Port 25 : not offered by Brevo
Mixing them up, 465 with TLS selected, fails before authentication is even attempted, and can surface the same generic message.
Connectivity is essentially never the cause, so rule it out first. From any machine:
python3 - <<'PY'
import smtplib
s = smtplib.SMTP("smtp-relay.brevo.com", 587, timeout=15)
print(s.ehlo("test.local"))
s.starttls()
print("STARTTLS ok")
PY
If that prints 250 and STARTTLS ok, the server is reachable and offers AUTH; the problem is
the credentials. Test the credentials directly with s.login(login, key) and read the SMTP reply, which is
more specific than the message a mail client shows you.
[ID]@smtp-brevo.com