# Discourse notification e-mail sending with Brevo(Sendinblue)

**URL:** <https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342>\
**Category:** Self-hosting\
**Tags:** email\
**Created:** [May 16, 2024, 10:45pm UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342 "2024-05-16T22:45:31Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Architect](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/architect/32/520575_2.png) [@Architect](https://meta.discourse.org/u/Architect)\
**Post date:** [May 16, 2024, 10:45pm UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/1 "2024-05-16T22:45:31Z")

</div>

Good day, fellow discoursians!!

Have setup discourse site to send e-mail with brevo which is working perfectly, except that e-mails are being flagged with this alert:

 ![Udklip brevo](https://global.discourse-cdn.com/meta/original/4X/a/6/3/a633e12d0dfd226161c3d99561d6910c495100b3.jpeg)

("We could not prove that the content or sender of this message is valid. The technical sender is: bounces ####…)

Believe this is not a problem with discourse itself, but need to correctley configure e-mail sending so that recievers can validate notification mail as being valid.

Can reach out to Brevo support about this but just checking here in case anyone may know what causes this to happen with e-mail senders in general, not just brevo. Didn’t have this problem when e-mail sending with mailgun but there were some other challenges with that platform.

---

_[View the full topic](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342)._