I used to send emails from Reply.io and Bcc them to Hubspot. Everything worked fine until yesterday morning (25 July). Since then, any emails that are sent from Reply.io and Bcc’ed to Hubspot don’t get captured within Hubspot.
I tried taking the email that Reply.io sent (which appears in my Sent mail) and forward it to Hubspot’s Fwd address, but it still doesn’t get captured.
If I compose a new email message in Gmail and Bcc it to Hubspot, the Bcc address works just fine.
Anyone else having this issue? Has Hubspot started to block emails that have reply.io in their header?
- I compose an email in my mail client and send it from abc@xyx.com to jon.doe@xyz.net, Bcc hubspot and it gets captured
- I send the same email through reply.io, it shows up in my “sent mail” as sent from abc@xyx.com to jon.doe@xyz.net, Bcc hubspot, but it doesn’t get captured.
Furthermore, even if I forward the Reply.io email from my mail client to the Hubspot fwd address, it still does not get captured. If I forward any other message, it gets captured.
The only difference between the two emails is that the latter has reply.io in the headers. So neither the Bcc nor the Fwd work.
Any ideas?
PS - This started happening one morning, in the midst of a Reply.io campaign, without me making any changes anywhere.
I don’t have a reply.io extension installed anywhere… All emails are sent from the reply.io website.
Nor do I have a hubspot extension installed on my Mac… I compose & send emails through Mac Mail.
So I don’t think this has anything to do with extensions.
It seems to me that emails arrive in the Hubspot Bcc/Fwd account, but they are not picked up by Hubspot if the email message was originally sent from the reply.io service.