# 使用Brevo（Sendinblue）发送Discourse通知电子邮件
**URL:** https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342
**Category:** Self-hosting
**Tags:** email
**Created:** [2024年五月16日 22:45 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342 "2024-05-16T22:45:31Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Architect](https://meta.discourse.org/u/Architect)
#### Post date: [2024年五月16日 22:45 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/1 "2024-05-16T22:45:31Z")
各位 Discourse 用户，日安！
已将 Discourse 站点设置为使用 Brevo 发送电子邮件，并且工作正常，只是电子邮件被标记为带有此警报：
（“我们无法证明此消息的内容或发件人是有效的。技术发件人是：bounces ####…)”）
我认为这不是 Discourse 本身的问题，但需要正确配置电子邮件发送，以便收件人能够验证通知邮件的有效性。
可以联系 Brevo 支持部门解决此问题，但在此处检查一下，以防有人知道是什么原因导致电子邮件发件人（不仅仅是 Brevo）出现这种情况。使用 Mailgun 发送电子邮件时没有遇到此问题，但该平台存在其他一些挑战。
---
### Author:  [@Architect](https://meta.discourse.org/u/Architect)
#### Post date: [2024年六月26日 04:59 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/2 "2024-06-26T04:59:59Z")
此外，关于这个主题，今天从 Brevo 看到一个新警报：
> **[Comply with Gmail, Yahoo, and Microsoft's requirements for email senders](https://help.brevo.com/hc/en-us/articles/14925263522578-Comply-with-Gmail-Yahoo-and-Microsoft-s-requirements-for-email-senders)**
>
> 💡 Need help setting up your requirements?
> Hire a Brevo Certified Expert to ensure your setup is smooth and compliant with Gmail, Yahoo, and Microsoft's requirements!
> Hire a Brevo Expert
>
>
> Since Feb...
将通过支持指南了解如何满足这些要求。
---
### Author:  [@ashishdungdung](https://meta.discourse.org/u/ashishdungdung)
#### Post date: [2024年八月12日 14:40 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/3 "2024-08-12T14:40:21Z")
我为客户配置了相同的内容，但没有遇到上述问题。不过，所有账户都会收到此通知。
---
### Author:  [@Architect](https://meta.discourse.org/u/Architect)
#### Post date: [2024年八月13日 01:25 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/4 "2024-08-13T01:25:21Z")
您检查过 DKIM 签名和 DMARC 状态了吗？
---
### Author:  [@Architect](https://meta.discourse.org/u/Architect)
#### Post date: [2024年八月21日 04:37 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/5 "2024-08-21T04:37:05Z")
从支持部门获得了答复：问题在于子域需要进行身份验证，根域身份验证也需要。我之前不知道这一点。需要按照步骤完成该过程。
---
### Author:  [@Architect](https://meta.discourse.org/u/Architect)
#### Post date: [2024年八月29日 18:20 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/6 "2024-08-29T18:20:07Z")
以下是 Brevo 的官方指南：
> **[Authenticate your domain with Brevo (Brevo code, DKIM, DMARC)](https://help.brevo.com/hc/en-us/articles/12163873383186-Authenticate-your-domain-with-Brevo-Brevo-code-DKIM-DMARC)**
>
> ❗️ Important
> Since February 1, 2024, domain authentication is mandatory as part of Gmail and Yahoo's requirements for email senders. On May 5, 2025, Microsoft announced it would adopt similar stand...
> **[Create a new sender (From name and From email)](https://help.brevo.com/hc/en-us/articles/208836149-Create-a-new-sender-From-name-and-From-email?source=search)**
>
> Choosing a sender for your emails is an important step. The sender is visible in your recipients' inboxes, helping them quickly identify who you are and making them confident in opening your email....
为邮件子域设置 DKIM、DMARC 和 DNS 记录以进行邮件和发件人身份验证是一个相当简单的过程。
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [2024年九月28日 18:20 UTC](https://meta.discourse.org/t/discourse-notification-e-mail-sending-with-brevo-sendinblue/308342/7 "2024-09-28T18:20:37Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.