Notification > Notification Hub > Usage Policy and Preset Guide > Email
To send emails from Notification Hub, you must have an sending domain of your own, so that each user can authenticate the sender's identity through their domain and that the email is not classified as spam. E-mail reliability can be enhanced by applying authentication settings such as SPF, DKIM, and DMARC through the sending domain. This allows e-mail to reach the receiver's mailbox safely and prevent phishing or spoofing. Through Notification Hub email sending (SMTP) server, an email is sent to the receiving server (SMTP) with an email address containing your own domain. For the email receiving server to trust Notification Hub email sending server, the SPF, DKIM, and DMARC TXT record settings are required in DNS where the user-owned domain is served.
The sender policy framework (SPF) is an authentication mechanism that defines a list of allowed servers when sending emails to prevent spam or phishing attacks that falsify sending domains. By adding an SPF record to the DNS of the sending domain, the email receiving server can authenticate whether the email was sent from the servers included in that list. This increases the confidence of the emailing server and prevents emails from being classified as spam.
Domain Keys identified mail (DKIM) is an authentication method that adds a digital signature to an email to prove that the sending domain is not forged. The email sending server adds an email header containing the signature, and the email receiving server verifies the validity of the signature through the public key in the sending domain. This ensures that the email is not tampered with during transmission and increases the reliability of the sender and email sending server.
Domain-based message authentication, reporting, and conformity (DMARC) is a way to strengthen email authentication based on SPF and DKIM, and to define in policy how emails that fail to authenticate will be handled. Domain owners provide policies (reject, isolate, allow) to handle emails in the event of an authentication failure on the email receiving server through DMARC. The report feature also enables DMARC to receive report emails from email receiving servers about authentication failure cases, which it analyzes to help enhance domain protection.
Starting February 1, 2024, Gmail and Yahoo's email sender guidelines has changed to deny sending requests to some incoming mail systems if domain authentication and SPF, DKIM, and DMARC authentication are not completed. As a result, sending to Gmail and Yahoo will fail for sending domains that have not completed SPF, DKIM, and DMARC authentication in Notification Hub.
Gmail uses domain reputation as the primary criterion for spam mail decisions. If a sender with a low domain reputation sends a large number of emails at a high speed or an advertising email that the receiver does not want, it will be stored in the receiver's inbox, but it will be able to display alerts or store them in the spam mailbox, and furthermore, it will be able to slow down or deny reception at all. Therefore, if you want to send an email in bulk, always be careful to keep your domain reputation high by referring to the following guide
If the receiver's email is Gmail, it is not possible to collect whether the email is viewed or not. Typically, the image tag is inserted into the body of the email to verify the receiver's email viewing, but Gmail modifies the body of the email to prevent the image proxy server from caching and tracking the image. This was intentionally blocked by Gmail, and it is currently not technically possible to collect events for such viewing.
Be informed - Gmail Image Proxy
Because the Gmail Image Proxy service does not forward users' cookies, you can't use the measurement protocol to track Gmail users. The Gmail Image Proxy service prevents this by having the measurement protocol requests passed through an intermediate server.
This is a brief guide to Gmail reputation criteria. Learn how Gmail evaluates reputation and learn how to raise and maintain reputation. For more information, read the references below.
When sending mail, the ISP (inbox service provider, Gmail, incoming SMPT server) evaluates the reputation of the sending SMTP server to determine whether it is received or not, and classifies spam. If you send mail that does not fit your ISP's reputation evaluation method, it can slow down the sending speed or make it difficult for recipients who use that ISP to receive mail.
Reputation can be largely divided into, IP reputation and domain reputation. * IP Reputation: IP is the IP of the sending SMTP. It means the reputation of the IP of the sending SMTP. * Domain Reputation: The domain is the mail sending domain. The domain of NHN will be 'nhn.com '. It refers to the reputation of the domain that is responsible for sending mail.