# Error in reply via email

**URL:** <https://meta.discourse.org/t/error-in-reply-via-email/171723>\
**Category:** Support\
**Created:** [November 30, 2020, 11:49am UTC](https://meta.discourse.org/t/error-in-reply-via-email/171723 "2020-11-30T11:49:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![developerbishal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/developerbishal/32/188919_2.png) [@developerbishal](https://meta.discourse.org/u/developerbishal)\
**Post date:** [November 30, 2020, 11:49am UTC](https://meta.discourse.org/t/error-in-reply-via-email/171723/1 "2020-11-30T11:49:41Z")

</div>

I have a working installation of Discourse setup. I have a Sendgrid account setup that is working with this installation. Discourse is successfully sending out verification emails and topic replies. However I am using Gsuite POP3 for reply via Email. For instance when I try to reply to a topic by using the “reply to this email to respond” contained in the email, I get an following error message:

Email Subject: Email issue – Unknown To:Address  
Message: [[We’re sorry, but your email message to [“general-community@example.com”] (titled Test email) didn’t work. Do you use more than one email address? Did you reply from a different email address? Email replies require that you use the same email address when replying. Alternately, the Message-ID header in the email may have been modified.]]

We are constantly having Discourse miss emails completely when they should be either a reply or starting a new topic, without any errors. Can anyone suggest cause and possible solution to above reply via email error ?

---

<div class="post-metadata">

**Author:** ![Tech\_Boy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tech_boy/32/198954_2.png) [@Tech\_Boy](https://meta.discourse.org/u/Tech_Boy)\
**Post date:** [November 30, 2020, 12:28pm UTC](https://meta.discourse.org/t/error-in-reply-via-email/171723/2 "2020-11-30T12:28:39Z")

</div>

Desperately waiting for solution. I am also facing same issue in my site.
