A user discusses issues with Brevo (Sendinblue) email notifications being flagged as invalid, despite successful email delivery. The problem appears to stem from improper domain authentication, particularly involving sub-domain verification. The user initially sought advice on whether this was a general email sender issue, then discovered the need to authenticate the sub-domain in addition to the root domain. After consulting Brevo’s support and documentation, the user confirmed that setting up DKIM, DMARC, and DNS records for the mail sub-domain resolves the issue. Other users noted similar notifications but didn’t face the same problems, highlighting the importance of proper email authentication. Architect shares the official Brevo guides for domain authentication, emphasizing the steps needed to ensure email validation. ashishdungdung mentions experiencing similar alerts but not the same issues, while Architect prompts checking DKIM and DMARC status. Architect confirms the solution involves sub-domain authentication, and Architect provides links to Brevo’s official setup guides.
("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.
Got answer from support: problem is that sub-domain needs to be authenticated in addition to the root domain authentication. Didn’t know about that. Need to go through the steps to complete that process.
