Ever since moving off of another email platform to HighLevel, our deliverability hasn't been as good. We've had many people mention they weren't getting our emails, even though our domain (and MailGun IP) isn't blacklisted anywhere and we've historically had an impeccable sender reputation for many years. (We also design our email messaging to avoid being marked as spam.)

We've come to realize it's because HighLevel seems to force us to send from a subdomain of our main email domain (probably for message tracking purposes within HighLevel) which is not common in most email platforms.

Here's a literal response from one of our recipient's IT staff about why our emails (sent via HighLevel) weren't getting through to her:

"The emails they sent were being blocked because the email header includes both domains – TheirDomain.com & email.TheirDomain.com – which throws a flag in the phishing AI. Our security checks include following all links in the email and looking for re-directs and mis-matches in header information which could indicate a spoofed email address."

There could be various ways for HighLevel to address this issue, but right now it looks like the most direct way to address this outright would be to allow us to send from our actual mail domain vs being forced to setup and send from a subdomain. I have a feeling with the way security is going, this will only become more of an issue for all us HighLevel users who rely on the system to send emails.

(Such a solution would also avoid another current issue where recipients replying to our emails aren't actually replying to the "from" address and instead are sending an email back to the subdomain, hence not making it to the actual inbox of the "from" sender address. We don't care about tracking these in HighLevel's CRM functionality anyway... and if we did, there are typically other viable solutions like email client plugins to handle that.)