# Bounced emails not being detected

**URL:** <https://meta.discourse.org/t/bounced-emails-not-being-detected/293518>\
**Category:** Product Support\
**Tags:** email\
**Created:** [January 30, 2024, 6:36pm UTC](https://meta.discourse.org/t/bounced-emails-not-being-detected/293518 "2024-01-30T18:36:10Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)\
**Post date:** [February 7, 2024, 1:19am UTC](https://meta.discourse.org/t/bounced-emails-not-being-detected/293518/17 "2024-02-07T01:19:15Z")

</div>

Thanks. That’s super helpful.

So basically the `reply_by_email_address` is used in the from header so that it comes back to that email address if it bounces. And the same email address is also set on the reply-to header if replies by email are enabled.

So, if my understanding above is correct, then if discourse can have a separate setting (`reply_to_email`) for the `reply-to` header, then that would solve the issue for the DMARC failure. When using the [yyy.com](http://yyy.com) domain (taken from `reply_by_email_address`) for `from` while sending and [gmail.com](http://gmail.com) for the `reply-to` (taken from the a new `reply_to_email` setting). If the email bounces it will still be returned to the `reply_by_email_address` but if the user replies then it would go to `reply_to_email`.

---

_[View the full topic](https://meta.discourse.org/t/bounced-emails-not-being-detected/293518)._
