Gmail requirements details
Posted: Thu Feb 20, 2025 6:17 am
From here on, we will explain the content and response methods for each requirement.
SPF/DKIM support for sender domains
SPF and DKIM are both "sending domain authentication" to prove that emails are not spoofed . By setting up these authentications, you can prove that emails are sent from the correct sender(※).
DKIM is performed on the domain of the email sender (the domain albania mobile database part of the sender's From address). A dedicated record is required, and if you operate your own mail server, you will obtain it yourself, and if you use an external service such as a rental server or mail delivery system, you will obtain it through that service.
If you are using an email delivery service, we recommend that you set DKIM to "author signature" rather than "third-party signature ." This is because it requires "author signature" when combined with DMARC, which will be described later.
*For further details, please see our article below.
DMARC support for sender domains
DMARC is also one of the "sender authentication" methods to prove that the email is not spoofed .
In relation to another requirement regarding DMARC described below, it is a mechanism that is more effective when used in combination with SPF and DKIM. Specifically, it allows the sender to control how the receiver handles spoofed email. There are three ways to handle it:
● none: Do nothing
● quarantine: Isolate
● reject: Do not accept
For example, if the sender sets "reject" beforehand, it will be possible to prevent the recipient from unknowingly receiving spoofed emails. However, even if the email is legitimate, it will not be received if the sender domain authentication settings are incorrect.
SPF/DKIM support for sender domains
SPF and DKIM are both "sending domain authentication" to prove that emails are not spoofed . By setting up these authentications, you can prove that emails are sent from the correct sender(※).
DKIM is performed on the domain of the email sender (the domain albania mobile database part of the sender's From address). A dedicated record is required, and if you operate your own mail server, you will obtain it yourself, and if you use an external service such as a rental server or mail delivery system, you will obtain it through that service.
If you are using an email delivery service, we recommend that you set DKIM to "author signature" rather than "third-party signature ." This is because it requires "author signature" when combined with DMARC, which will be described later.
*For further details, please see our article below.
DMARC support for sender domains
DMARC is also one of the "sender authentication" methods to prove that the email is not spoofed .
In relation to another requirement regarding DMARC described below, it is a mechanism that is more effective when used in combination with SPF and DKIM. Specifically, it allows the sender to control how the receiver handles spoofed email. There are three ways to handle it:
● none: Do nothing
● quarantine: Isolate
● reject: Do not accept
For example, if the sender sets "reject" beforehand, it will be possible to prevent the recipient from unknowingly receiving spoofed emails. However, even if the email is legitimate, it will not be received if the sender domain authentication settings are incorrect.