# \[DONE\] Include Reply-To header in message entities from email integration

**URL:** https://community.fibery.io/t/done-include-reply-to-header-in-message-entities-from-email-integration/3189
**Category:** Integrations
**Tags:** email-integration
**Created:** [August 19, 2022, 3:38pm UTC](https://community.fibery.io/t/done-include-reply-to-header-in-message-entities-from-email-integration/3189 "2022-08-19T15:38:02Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Oliver](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oliver/32/5403_2.png) [@Oliver](https://community.fibery.io/u/Oliver)
#### Post date: [August 19, 2022, 3:38pm UTC](https://community.fibery.io/t/done-include-reply-to-header-in-message-entities-from-email-integration/3189/1 "2022-08-19T15:38:02Z")

</div>

We’re using the email integration to sync emails from a gmail account as part of our support process. Some of the emails are sent by customers via google groups, meaning they arrive in the sync’d inbox with the “From” header being the google group email, and the “Reply-To” header being the customer’s email. When the messages are imported, only the “From” value is included, which means we lose the link between the customer’s contact entity and the message entity.

If the “Reply-To” header could be included as part of the import of messages in the email integration, then we could easily see support queries linked to customer contact entities.

---

<div class="post-metadata">

### Author: ![Oliver](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oliver/32/5403_2.png) [@Oliver](https://community.fibery.io/u/Oliver)
#### Post date: [September 5, 2022, 10:23am UTC](https://community.fibery.io/t/done-include-reply-to-header-in-message-entities-from-email-integration/3189/2 "2022-09-05T10:23:23Z")

</div>

After a little more exploration of the email headers available in these scenarios, we’ve discovered that X-Original-Sender maybe be a better option than Reply-To. Reply-To can sometimes refer to “infrastructural” email addresses depending on the senders mail server setup. Whereas X-Original-Sender seems to always be the email address intended for public consumption. I.e. with Fibery staff emails, X-Original-Sender will be say “[polina@fibery.io](mailto:polina@fibery.io)” but Reply-To will be “[polina.zenevich@fibery.intercom-mail.com](mailto:polina.zenevich@fibery.intercom-mail.com)”

---

<div class="post-metadata">

### Author: ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [September 20, 2024, 6:01am UTC](https://community.fibery.io/t/done-include-reply-to-header-in-message-entities-from-email-integration/3189/3 "2024-09-20T06:01:57Z")

</div>

This was implemented in one of the latest releases, but I am not sure about X-Original-Sender, it seems From field is set correctly if a person sends an email to a group.

> [@Sep 5, 2024 / dashing\_away Updated Entity View Header & Go-to navigation, Reorder rules & buttons, Lock Whiteboard](https://community.fibery.io/t/sep-5-2024-updated-entity-view-header-go-to-navigation-reorder-rules-buttons-lock-whiteboard/6598):
>
> This release is dedicated to polishing and small improvements in many areas. metal Updated Entity View Header Entity View header was updated to match new Views headers released last week. Multiple Entity Views switcher is more visible, panel navigation is moved to the right, and you can jump to space fron any entity with a single click. dash Go-to navigation from Entity View We’ve added a Go-to navigation on Entity View (find \>\> icon in the top right corner). You can quickly jump…
