Troubleshooting internal email being marked as spam

Edited

Overview

If you are experiencing issues with internal email sent via Front landing in your colleagues' spam folders, take a look at some of the common causes below to troubleshoot this.

This article applies to email addresses connected to Front via SMTP forwarding. If your email channel uses Gmail sync or Office 365 sync, this does not apply.


Common causes

Missing proper SPF/DKIM DNS records

You may need to update your deliverability settings and create the required DNS records for Front. Failure to do this can result in recipient mail servers (including your own) classifying incoming mail as not being authorized to be sent via your domain, resulting in the mail being rejected or marked as spam.

Configuring these DNS records often helps resolve these problems.

Mail server is not expecting mail from Front

Some mail servers maintain a list of IP addresses they expect internal mail to originate from. If your mail server maintains such a list, internal mail may be rejected by the mail server when sent via Front if Front's IPs have not been added to this list. Please have your IT administrator reach us through our contact form if you believe this is the case.