Understanding Gmail's New Sender Requirements

What's changed?

The most significant change comes from enhanced email authentication protocols, which are designed to strengthen proven ownership of email domains and establish you as the real sender. These new guidelines require the implementation of the following email authentication protocols.

  • SPF (Sender Policy Framework): This protocol validates emails by verifying that they are sent from authorized domains. It’s crucial for preventing email spoofing.
  • DKIM (DomainKeys Identified Mail): This adds a digital signature to each email, ensuring its authenticity and that it hasn’t been tampered with during transmission.
  • DMARC (Domain-based Message Authentication Reporting & Conformance): This policy framework utilizes SPF and DKIM to provide a comprehensive email authentication approach, reporting discrepancies and non-compliance.
Custom SMTP users

For Re:amaze users, compliance with Gmail's updated policies is tied to the use of Custom SMTP. With Custom SMTP enabled, emails are being sent from your domain, so you will need to ensure that your domain follows the new Gmail sender rules and requirements. To satisfy these requirements, make sure that you have SPF, DKIM, and DMARC set up.

Non-Custom SMTP users

If you don't have Custom SMTP enabled, your emails are sent via a Re:amaze domain (e.g. support@acme.reamaze.com). In this case, we recommend adding an SPF record for Re:amaze's domain to send emails on your behalf. More information on how to do that can be found in this article. Having SPF configured correctly will ensure compliance with Gmail's sender policies.

If you have any questions regarding compliance with Gmail's updated sender policies, feel free to contact us at support@reamaze.com.

Contact Us

Not finding what you're looking for? Contact Us Directly