The end of my relationship with hey.com may be sooner than I ever envisaged.
I've tried to adopt their new way of using email and mostly have enjoyed the challenge, but one thing has both disappointed and surprised me, fixing a major issue.
Forwarding email away from hey.com still doesn't work!
Back in January I decided to use the function in hey.com to forward my email to my Gmail.com account, not all the emails were forwarded, so I tried the same to my iCloud.com address and the same problem accrued.
I emailed their support and they replied stating the issue was caused by my emails being quite spammy. This just wasn't the case so I decided to investigate the issue myself, I ran tests and spent a while comparing headers. Then wrote a comprehensive blog post and shared it with their support team via email and Twitter.
It took a while for them to acknowledge there was indeed a problem, but after a week or so the issue still existed so I tweeted them again and chased via email. I then received a group of replies and one from a Basecamp programmer who said he was working on the issue and would I help them run some tests, of course I agreed.
We are now on March 8th and today I setup the forwarder again and the exact same issue still exists, see screen grab below.
The problem is being caused with how they forward emails is breaking the DKIM signing, which in turn is causing DMARC to tell the receiving server to reject the emails.
I am sure all that is needed is for them to implant ARC headers, which seal the original authentication.
Trust me when I say I really want this to work for me, but a tech firm the size of basecamp.com shouldn't have had this issue in the first place. One of their selling points is that if you don't renew your subscription after the 1st year they will forward your @hey.com email to an alternative address for free, forever.
