Forwarding email out of HEY
Let’s start with our general advice: you shouldn’t rely on forwarding alone for critical or very important emails. If you close your @hey.com account, you can set up forwarding so you won’t miss anything if someone accidentally sends emails to your old @hey.com address, but this is not meant to be actively used in perpetuity. You should move any important services where you still have your @hey.com account configured to use an active email address instead.
If you have a HEY For Domains account and you need to receive critical mail in any of your domain addresses, configure it as a regular user or extension instead of an external extension. As a regular user, you can still forward to an external address while being able to log in and access emails directly.
- HEY won’t forward emails classified as spam.
If our spam filters determine that an email is spam, we won’t forward it out. Although they’re rare, false positives happen and we might flag a legit email as spam and skip forwarding it.
- Forwarding might break email authentication.
Depending on the sender’s domain configuration and the receiver’s email service, an automatically forwarded email might not arrive, or it might be flagged as spam when it reaches the recipient. The reason is that email forwarding can break DMARC. To help with this, we implement ARC authentication for forwarded emails. This preserves SPF and DKIM authentication for the original emails and, thus, reduces the likelihood that forwarded messages are flagged as spoofed. However, ARC doesn’t always work, as the receiver might decide not to trust the ARC headers. This is very unlikely, but it might happen.
If you have any questions, send us an email at email@example.com and we’ll help you out.