Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
email_protection_resources [2018/01/14 09:08] Stephane de Labrusse [Email Methods: Helo, DNS, Domain reputation, Blacklist SPF, DKIM, DMARC and ARC] |
email_protection_resources [2021/03/23 18:02] (current) Stephane de Labrusse [How to check it ?] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Email Methods: Helo, DNS, Domain reputation, Blacklist SPF, DKIM, DMARC and ARC ====== | + | ====== Email Methods: Helo, DNS, Domain/IP reputation, Blacklist SPF, DKIM, DMARC and ARC ====== |
The email server is a central communication hub for your company. It needs to be protected and secured against spam, but also you must be sure that your emails are correctly delivered to your recipients and not rejected or tagged as spam by other platforms like Google Apps, Outlook 365, etc. | The email server is a central communication hub for your company. It needs to be protected and secured against spam, but also you must be sure that your emails are correctly delivered to your recipients and not rejected or tagged as spam by other platforms like Google Apps, Outlook 365, etc. | ||
- | Around an Email Server, you have always methods to verify the emails are not sent by a spam host, like SPF, DKIM, DMARC, rDNS: This is what we will talk. In all probability if you do not configure properly all of these authentication methods your email will be refused. | + | Around an Email Server, you have always methods to verify the emails are not sent by a spam host, like SPF, DKIM, DMARC, rDNS: This is what we will talk. In all probability if you do not configure properly all of these authentication methods your email will be refused. For the impatient, they can check now and see what they have to configure: go to https:// |
- | For the impatient, they can check now and see what they have to configure: go to https://www.mail-tester.com and send an email to the address given (only three free tests per day). Think to remove your smarthost sender if you have one configured. | + | It is easy to install and create a mail server with nethserver, but you must configure |
<WRAP center round important 60%> | <WRAP center round important 60%> | ||
Line 15: | Line 15: | ||
<WRAP center round tip 60%> | <WRAP center round tip 60%> | ||
- | If your domain is registered to a public | + | If the domain |
</ | </ | ||
Line 38: | Line 38: | ||
The purpose of DNS is to use easy to remember domain names for websites instead of their numeric IP addresses. It also enables website owners to change their web hosts without changing domain names. Website owners can simply change the DNS entry for their domain name and point to their new web host’s name servers. | The purpose of DNS is to use easy to remember domain names for websites instead of their numeric IP addresses. It also enables website owners to change their web hosts without changing domain names. Website owners can simply change the DNS entry for their domain name and point to their new web host’s name servers. | ||
- | <WRAP center round todo 60%> | + | |
- | It is easy to install and create a mail server with nethserver, but you need to configure the dns zone of your domain in the settings of your public dns provider, we want to explain all the mandatory dns records. | + | |
- | </ | + | |
- | + | ||
===== DNS ===== | ===== DNS ===== | ||
- | All settings must propagated to all DNS server of the world, it needs time to be known by all. So be patient and wait 24 hours after each change. By experience we know that the google | + | All settings must propagated to all DNS server of the world, it needs time to be known by all. So be patient and wait 24 hours after you have changed your records. By experience we know that the google |
==== A record ==== | ==== A record ==== | ||
Line 58: | Line 55: | ||
This is an example at 1&1 {{:: | This is an example at 1&1 {{:: | ||
- | ===How to check it=== | + | ===How to configure it ?=== |
+ | ask to google | ||
+ | < | ||
+ | set A record YourDnsProvider | ||
+ | </ | ||
+ | |||
+ | ===How to check it ?=== | ||
The domain must be tested | The domain must be tested | ||
Line 74: | Line 77: | ||
164.132.xxx.xxx | 164.132.xxx.xxx | ||
</ | </ | ||
+ | |||
=== sub.domain.com === | === sub.domain.com === | ||
- | Nethserver creates several sub domain by default to be reached from outside or internally (check / | + | Nethserver creates several sub domain by default to be reached from outside or internally (check / |
**At minimal you must create these sub.domains and set the ' | **At minimal you must create these sub.domains and set the ' | ||
Line 99: | Line 103: | ||
< | < | ||
- | mail.domain.com | + | prometheus.domain.com |
+ | smtp.domain.com | ||
+ | mail.domain.com | ||
</ | </ | ||
- | ===How to check it=== | + | ===How to configure it ?=== |
+ | ask to google | ||
+ | < | ||
+ | set A record YourDnsProvider | ||
+ | </ | ||
+ | |||
+ | ===How to check it ?=== | ||
Each subdomain must be tested | Each subdomain must be tested | ||
Line 122: | Line 134: | ||
MX record is abbreviation for Mail Exchanger record. It is a type of DNS resource record that defines a mail server to handle email for a particular domain name. For example, by adding an MX recorded to mail.domain.com for your domain.com, any email received by your domain.com will be handled through your mail servers. | MX record is abbreviation for Mail Exchanger record. It is a type of DNS resource record that defines a mail server to handle email for a particular domain name. For example, by adding an MX recorded to mail.domain.com for your domain.com, any email received by your domain.com will be handled through your mail servers. | ||
- | The MX record is checked if there is a mail server (MX Record) behind your domain name, often spam sender do not have it properly configured. The MX record(s) must be added to your public | + | The MX record is checked if there is a mail server (MX Record) behind your domain name, often spam sender do not have it properly configured. The MX record(s) must be added to your public |
<WRAP center round tip 60%> | <WRAP center round tip 60%> | ||
Line 140: | Line 152: | ||
This is an example at 1&1 | This is an example at 1&1 | ||
{{:: | {{:: | ||
- | ===How to check it=== | + | ===How to configure it ?=== |
+ | ask to google | ||
+ | < | ||
+ | set MX record YourDnsProvider | ||
+ | </ | ||
+ | |||
+ | ===How to check it ?=== | ||
* Web tools | * Web tools | ||
Line 165: | Line 183: | ||
For instance, it’s important how old is the domain. In fact, for the first 5 days after a new domain was registered, it is by default considered as suspicious. After all, reputation is something you can only earn over time. So it’s good to warm up all the emails on such a fresh domain by sending just a few emails per day during the first 2-3 weeks after the registration. | For instance, it’s important how old is the domain. In fact, for the first 5 days after a new domain was registered, it is by default considered as suspicious. After all, reputation is something you can only earn over time. So it’s good to warm up all the emails on such a fresh domain by sending just a few emails per day during the first 2-3 weeks after the registration. | ||
- | Good reputation of your domain increases the deliverability of your emails. That’s why it’s important to have it checked through blacklists and fix all the dns records you will read below, then test your domain score by http:// | + | Good reputation of your domain increases the deliverability of your emails. That’s why it’s important to have it checked through blacklists and fix all the DNS records you will read below, then test your domain score by http:// |
{{:: | {{:: | ||
Line 186: | Line 204: | ||
- | ====How to check it==== | + | ====How to check it ?==== |
* Web tools | * Web tools | ||
Line 206: | Line 224: | ||
==== How to configure it ?==== | ==== How to configure it ?==== | ||
- | In the Public | + | In the Public |
This is what it looks at soyoustart | This is what it looks at soyoustart | ||
Line 216: | Line 234: | ||
- | ====Examples of configuration==== | + | ====How to configure it ?==== |
Ask to google | Ask to google | ||
< | < | ||
- | PTR record YourIpProvider | + | set PTR record YourIpProvider |
</ | </ | ||
- | ====How to check it==== | + | ====How to check it ?==== |
* Web tools | * Web tools | ||
- | You can check if your reverse | + | You can check if your reverse |
* In the terminal | * In the terminal | ||
Line 239: | Line 257: | ||
</ | </ | ||
+ | You can check also by comparing this two commands in the terminal | ||
+ | |||
+ | < | ||
+ | / | ||
+ | reverseIP. | ||
+ | / | ||
+ | publicIP. | ||
+ | </ | ||
+ | |||
+ | the reverseIP. found must match the publiIP retrieved in the second command line. | ||
=====SPF and SenderID===== | =====SPF and SenderID===== | ||
Line 249: | Line 277: | ||
====How to configure it?==== | ====How to configure it?==== | ||
- | All you have to do is in the dns zone of your domain name. This is a list of [[https:// | + | All you have to do is in the DNS zone of your domain name. This is a list of [[https:// |
- | add a record ' | + | add a record ' |
< | < | ||
Line 280: | Line 308: | ||
If your domain is under an SPAM attack trying to spoofing your domain, try to change the SPF to -all for a while, and reset to ~all when the attack ends. Keep selected the -all if you want to be strict with the SPF entry and you are sure that your DNS entry is correct. | If your domain is under an SPAM attack trying to spoofing your domain, try to change the SPF to -all for a while, and reset to ~all when the attack ends. Keep selected the -all if you want to be strict with the SPF entry and you are sure that your DNS entry is correct. | ||
- | ====Examples of configuration==== | + | ====How to configure it ?==== |
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
- | ====How to check it==== | + | ====How to check it ?==== |
* Web tools | * Web tools | ||
https:// | https:// | ||
Line 308: | Line 336: | ||
In technical terms, DKIM lets a domain associate its name with an email message by affixing a digital signature to it. Verification is carried out using the signer' | In technical terms, DKIM lets a domain associate its name with an email message by affixing a digital signature to it. Verification is carried out using the signer' | ||
====How to configure it?==== | ====How to configure it?==== | ||
- | Dkim is really simple with NethServer, go to the email panel and allow DKIM in the setting of your domain, then retrieve the digital key of this domain. Then this key must be saved in a **TXT record** in your (external) public | + | Dkim is really simple with NethServer, go to the email panel and allow DKIM in the setting of your domain, then retrieve the digital key of this domain. Then this key must be saved in a **TXT record** in your (external) public |
- | DKIM needs to be configured in the public DNS. You must create a **TXT** record ' | + | DKIM needs to be configured in the public DNS. You must create a **TXT** record '%%default._domainkey%%' or '%%default._domainkey.domain.com%%' in the DNS zone of your provider. **Your DKIM selector is default** |
< | < | ||
Line 319: | Line 347: | ||
{{:: | {{:: | ||
- | ====Examples of configuration==== | + | ====How to configure it ?==== |
* [[https:// | * [[https:// | ||
- | ====How to check it==== | + | ====How to check it ?==== |
* Web tools | * Web tools | ||
https:// | https:// | ||
Line 359: | Line 387: | ||
</ | </ | ||
- | ==== How to check it ==== | + | Here's a more complex DMARC entry for the test domain DMARC site: |
+ | |||
+ | < | ||
+ | v=DMARC1; p=quarantine; | ||
+ | </ | ||
+ | |||
+ | * The " | ||
+ | * The adkim and aspf options define how strictly DKIM and SPF policy should be applied, with ' | ||
+ | * The RUA provides an address for aggregate data reports, while the RUF provides an address for forensic reports | ||
+ | ==== How to check it ?==== | ||
* Web tools | * Web tools | ||