This section specifies requirements for applications that generate email.

[mdsojolh444]

In the world of the Internet, there are documents called RFCs that define various rules. There is also an RFC for email format, and RFC5322 is the latest version.

Most general applications are compliant, but just to be on thesafe albania mobile database side, send an email from the server or service you are using and check the following items in the header information of the received email.

The following email headers must not be duplicated
: To:, Cc:, Subject:, Date:, From:, Sender:, Reply-To:, Bcc:,
Message-ID:, In-Reply-To:, References:.
In reality, not all of these headers may be set in the email. For example, CC and BCC. In such cases, you can ignore them. The important thing is that "various email headers are not defined in duplicate . "

Do not spoof Gmail
This is a request to prohibit the use of gmail.com as a sending domain. This
also conflicts with the aforementioned "sending domain authentication" (SFP, DKIM, DMARC), so if you are using it, please switch to a different sending domain.

Add ARC or List:id headers when forwarding emails
This is a request to the MTA server that forwards email. This "forwarding" also includes expanding emails received by a mailing list to a Gmail address in the mailing list.
When forwarding, you need to set the ARC header for authentication when forwarding, and the List-id header for mailing lists .

This requirement is a little more complicated than the others, but if you are a sender of marketing emails, you can ignore it. This is because the recipient's MTA server is responsible for forwarding emails, and sending to a mailing list is a separate mechanism (not sending to a mailing list).