# 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:** 13

<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 6, 2024, 10:14pm UTC](https://meta.discourse.org/t/bounced-emails-not-being-detected/293518/13 "2024-02-06T22:14:31Z")

</div>

> [@supermathie](#):
>
> Doesn’t look like you’ve configured DKIM for `yyy.com`

Yes it’s configured and the email “sent” by discourse via the `yyy.com` SMTP server passes SPF, DKIM and DMARC without issues (atleast from the “Send test email” page in the admin console).

This issue is happening if I set a gmail address as the `reply_by_email_address` to a `gmail.com` address instead of the `yyy.com` address. Is there something I can do for this setup so that DMARC doesn’t fail when set to `reply_by_email_address` to a gmail address while keeping the outgoing server as `yyy.com` ?

> [@supermathie](#):
>
> For this to work, when Discourse sends a message, it needs to receive the reply to the address from which it came. Discourse looks in the `To:` header for this (not the envelope-to).

Can it not parse the rest of the content/attachments in the bounced email to extract that information if it can’t what it need in the “obvious” place (or atleast provide an option in settings to do that with the necessary warnings about impersonation)

---

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