DKIM is a mechanism that allows the email server to control the integrity of an email’s content and avoid any modifications during mail out.
During mail out, the eFlyerMaker’s server places in the header of the message an encrypted version of the lines FROM, TO, SUBJECT, REPLY TO, MESSAGE-ID. During reception, the servers applying this mechanism will interrogate the DNS of your domain and obtain the public key associated with our server in order to decrypt it. Again, the process reserved to emails who failed this test depends on the anti-spam policies of the server’s administrators.
Sender Policy framework (SPF)
Sender policy framework is a mechanism that allows the recipient’s email server to validate the legitimacy of the server that sent the message.
The recipient's server, equipped with this mechanism, will compare the IP source and the registered domain hidden in the header of the email, with the listed information under the SPF line of the domain name’s server where your domain resides. It is up to the recipient's server policy to decide what happens to a message that would fail that test. Some server administrators will apply a systematic rejection, others will put it in quarantine, or add the mention SPAM in the subject line.
Reverse NS Lookup
Mail exchange (MX) should allow us to find the legitimate answers from customers and system responses.
Many mail servers use rules controlling the different domain names that appear in the message header. All sent messages have a FROM header, a REPLY-TO header and a RETURN-PATH header. The email address listed in the RETURN-PATH header is typically used by mail servers to return the message to the sender when the recipient's address is invalid.
It is important for eFlyerMaker that invalid messages (bounces) are returned to our server. So, an email address must be placed, pointing to our server. However to avoid failure to the rule that the FROM field of the header must be the same as that of the header-RETURN PATH, we suggest adding a specific MX to our server. Without MX, returning messages will be sent directly to your server which prevents us from ensuring adequate monitoring of invalid recipients.
A Record is a sub domain that enables eFlyerMaker to track clicks and produce statistical reports.
Much like the rule of MX, strict spam filters will require that the hyperlinks domain name in the message is consistent with the domain of the email address FROM. It is a fundamental rule to detect phishing attempts. eFlyerMaker needs to transit links to its clickthrough tracking server before sending it to your domain’s site to properly accumulate link tracking statistics. Without A Record, clicks will be routed directly to their destination without tracking the statistical response rate.
The DMARC standard allows the recipient's mail server to determine the processing of messages received from your domain for mail servers that do not pass DKIM and SPF tests. On a daily basis, the domain administrator receives an xml report from the email servers adhering to this standard. The report contains information on the number of emails received with the FROM :. It indicates the IP source and the results of SPF and DKIM tests. The report also details how the server has managed the message afterward.