Understanding Gmail's Sender Requirements

Gmail requires email senders to implement the following authentication protocols to verify domain ownership and establish legitimacy:

• SPF (Sender Policy Framework): Validates emails by verifying they are sent from authorized domains. SPF helps prevent email spoofing by confirming that the sending server is permitted to send mail on behalf of your domain.
• DKIM (DomainKeys Identified Mail): Adds a digital signature to each email to verify its authenticity and confirm it has not been altered during transmission.
• DMARC (Domain-based Message Authentication Reporting and Conformance): A policy framework that uses both SPF and DKIM to provide a comprehensive approach to email authentication. It reports discrepancies and enforces compliance when either protocol fails.

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.