Wording.
This commit is contained in:
parent
f5b063bdf3
commit
27bfb682be
@ -171,8 +171,7 @@ show_error_title_label v = case v of
|
|||||||
|
|
||||||
show_error_login :: L.Error -> String
|
show_error_login :: L.Error -> String
|
||||||
show_error_login = case _ of
|
show_error_login = case _ of
|
||||||
L.ParsingError {error, position} ->
|
L.ParsingError {error} -> maybe "" string_error_login error
|
||||||
"position " <> show position <> " " <> maybe "" string_error_login error
|
|
||||||
|
|
||||||
string_error_login :: L.LoginParsingError -> String
|
string_error_login :: L.LoginParsingError -> String
|
||||||
string_error_login = case _ of
|
string_error_login = case _ of
|
||||||
@ -184,8 +183,7 @@ string_error_login = case _ of
|
|||||||
|
|
||||||
show_error_email :: E.Error -> String
|
show_error_email :: E.Error -> String
|
||||||
show_error_email = case _ of
|
show_error_email = case _ of
|
||||||
E.ParsingError {error, position} ->
|
E.ParsingError {error} -> maybe "" string_error_email error
|
||||||
"position " <> show position <> " " <> maybe "" string_error_email error
|
|
||||||
|
|
||||||
string_error_email :: E.EmailParsingError -> String
|
string_error_email :: E.EmailParsingError -> String
|
||||||
string_error_email = case _ of
|
string_error_email = case _ of
|
||||||
@ -197,8 +195,7 @@ string_error_email = case _ of
|
|||||||
|
|
||||||
show_error_password :: P.Error -> String
|
show_error_password :: P.Error -> String
|
||||||
show_error_password = case _ of
|
show_error_password = case _ of
|
||||||
P.ParsingError {error, position} ->
|
P.ParsingError {error} -> maybe "" string_error_password error
|
||||||
"position " <> show position <> " " <> maybe "" string_error_password error
|
|
||||||
|
|
||||||
string_error_password :: P.PasswordParsingError -> String
|
string_error_password :: P.PasswordParsingError -> String
|
||||||
string_error_password = case _ of
|
string_error_password = case _ of
|
||||||
|
@ -67,18 +67,22 @@ basics = HH.div_
|
|||||||
"""
|
"""
|
||||||
|
|
||||||
, Bulma.hr
|
, Bulma.hr
|
||||||
, Bulma.h3 "I have something to host."
|
, Bulma.h3 "I have something to host (A and AAAA records)."
|
||||||
, expl' "Let's assume you have a web server and you host your website somewhere (A and AAAA records)."
|
, expl' "Let's assume you have a web server and you host your website somewhere."
|
||||||
, Bulma.p """
|
, Bulma.p """
|
||||||
You want an A (IPv4) or AAAA (IPv6) record pointing to your server, named "enigma" for example.
|
You want an A (IPv4) or AAAA (IPv6) record pointing to your server, named "enigma" for example.
|
||||||
"""
|
"""
|
||||||
, expl' "You need other names pointing to your server (CNAME records)."
|
|
||||||
|
, Bulma.hr
|
||||||
|
, Bulma.h3 "You need other names pointing to your server (CNAME records)."
|
||||||
, Bulma.p """
|
, Bulma.p """
|
||||||
You may not want to use the name of your server "enigma" directly.
|
You may not want to use the name of your server "enigma" directly.
|
||||||
Instead, you may want the usual names for your services, such as "www" or "blog".
|
Instead, you may want the usual names for your services, such as "www" or "blog".
|
||||||
CNAME records are basically aliases, exactly to that end.
|
CNAME records are basically aliases, exactly to that end.
|
||||||
"""
|
"""
|
||||||
, expl' "If you have other servers, just add more A or AAAA records."
|
|
||||||
|
, Bulma.hr
|
||||||
|
, Bulma.h3 "If you have other servers, just add more A or AAAA records."
|
||||||
, Bulma.p """
|
, Bulma.p """
|
||||||
Tip: choose relevant names for your servers then add CNAME records.
|
Tip: choose relevant names for your servers then add CNAME records.
|
||||||
For example, you can have an A record named "server1" and a CNAME "www" pointing to it.
|
For example, you can have an A record named "server1" and a CNAME "www" pointing to it.
|
||||||
@ -91,7 +95,7 @@ basics = HH.div_
|
|||||||
, Bulma.h3 "I want an email server."
|
, Bulma.h3 "I want an email server."
|
||||||
, expl' """
|
, expl' """
|
||||||
Hosting a mail server is quite complex.
|
Hosting a mail server is quite complex.
|
||||||
This page will focus on the main parts regarding the DNS.
|
This section will focus on the main parts regarding the DNS.
|
||||||
"""
|
"""
|
||||||
, Bulma.notification_danger' """
|
, Bulma.notification_danger' """
|
||||||
The actual configuration of your mail server is complex and depends on your choice of software.
|
The actual configuration of your mail server is complex and depends on your choice of software.
|
||||||
@ -135,6 +139,12 @@ basics = HH.div_
|
|||||||
, Bulma.hr
|
, Bulma.hr
|
||||||
, Bulma.p """
|
, Bulma.p """
|
||||||
DMARC enables to check the "From:" field of a mail, based on the SPF and DKIM mechanisms.
|
DMARC enables to check the "From:" field of a mail, based on the SPF and DKIM mechanisms.
|
||||||
|
Thus, domains with a DMARC record enable to only allow verified mails.
|
||||||
|
Valid emails come from an authorized IP address (SPF), are signed by the verified email server (DKIM) and have an email address coming from a verified domain (DMARC) related to the two previous spam mitigation mechanisms.
|
||||||
|
"""
|
||||||
|
, Bulma.hr
|
||||||
|
, Bulma.p """
|
||||||
|
With DMARC, you won't accept an email from "hacker@example.com" because it was sent by another domain with a valid SPF and DKIM.
|
||||||
"""
|
"""
|
||||||
]
|
]
|
||||||
]
|
]
|
||||||
|
Loading…
Reference in New Issue
Block a user