Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
tutoriaux:install-email-server:install-email-server-part-5 [2023/01/06 16:41] – ↷ Page déplacée de tutoriaux:install-email-server-part-5 à tutoriaux:install-email-server:install-email-server-part-5 frater | tutoriaux:install-email-server:install-email-server-part-5 [2024/07/06 01:17] (Version actuelle) – frater | ||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
- | ====== | + | ====== Part 5 - DMARC to Protect Your Domain From Email Spoofing ====== |
- | In [[tutoriaux: | + | In [[tutoriaux: |
===== What is DMARC? ===== | ===== What is DMARC? ===== | ||
Ligne 25: | Ligne 25: | ||
==== 1. Create SPF and DKIM records ==== | ==== 1. Create SPF and DKIM records ==== | ||
- | Before creating a DMARC record, you must create [[tutoriaux: | + | Before creating a DMARC record, you must create [[tutoriaux: |
==== 2. Identifier alignment ==== | ==== 2. Identifier alignment ==== | ||
Ligne 97: | Ligne 97: | ||
A good service for DMARC test is https:// | A good service for DMARC test is https:// | ||
- | [[dmarc alignment test]] | + | [[..: |
Another way to test DMARC is send an email from your domain to your Gmail account. If DMARC is configured correctly then you will see **dmarc=pass** in the **authentication-results** header. (To view email headers in Gmail, click the '' | Another way to test DMARC is send an email from your domain to your Gmail account. If DMARC is configured correctly then you will see **dmarc=pass** in the **authentication-results** header. (To view email headers in Gmail, click the '' | ||
- | [[Gmail SPF and DKIM check scalahosting]] | + | [[..: |
To pass DMARC check, your emails need to meet one of the following requirements. | To pass DMARC check, your emails need to meet one of the following requirements. | ||
Ligne 129: | Ligne 129: | ||
Below is my first weekly report sent from Postmark. mcsignup.com belongs to MailChimp, which is what I use to send newsletters to my mailing list. In my SPF record, I actually allow MailChimp to send emails on my behalf, but I didn’t know that they don’t use my domain name in the Return-Path header for the signup confirmation emails. And they don’t sign emails using my DKIM domain. | Below is my first weekly report sent from Postmark. mcsignup.com belongs to MailChimp, which is what I use to send newsletters to my mailing list. In my SPF record, I actually allow MailChimp to send emails on my behalf, but I didn’t know that they don’t use my domain name in the Return-Path header for the signup confirmation emails. And they don’t sign emails using my DKIM domain. | ||
- | [[dmarc-report-analyzer-postmark]] | + | [[..:dmarc-report-analyzer-postmark]] |
There’s also an unknown source that claims to be linuxbabe.com. | There’s also an unknown source that claims to be linuxbabe.com. | ||
- | [[dmarc aggregate report]] | + | [[..: |
First, I always treat IP address that doesn’t have reverse DNS record as spam. Then, to identify other unknown sources, I will check if it’s on an email blacklist. debouncer.com tells me that it’s on 13 blacklists. So clearly it’s a spammer trying to impersonate my domain name. | First, I always treat IP address that doesn’t have reverse DNS record as spam. Then, to identify other unknown sources, I will check if it’s on an email blacklist. debouncer.com tells me that it’s on 13 blacklists. So clearly it’s a spammer trying to impersonate my domain name. | ||
- | [[identify unkown sources in DMARC report]] | + | [[..: |
To better understand the unknown source and how your domains are used, you can choose to receive forensic report by adding the ruf tag in DMARC record like below. | To better understand the unknown source and how your domains are used, you can choose to receive forensic report by adding the ruf tag in DMARC record like below. |