From a4678d0f33cdf1734e475fe8115ca5c2cdf6dcd0 Mon Sep 17 00:00:00 2001 From: Uwe Kamper Date: Sat, 10 Feb 2024 15:40:19 +0100 Subject: [PATCH] #881 add placeholder translation targets --- translations/en/main.po | 19 +++++++++++++++++++ translations/nl/main.po | 20 ++++++++++++++++++++ 2 files changed, 39 insertions(+) diff --git a/translations/en/main.po b/translations/en/main.po index 7a4039e44..91962e65a 100644 --- a/translations/en/main.po +++ b/translations/en/main.po @@ -588,6 +588,25 @@ msgstr "" "your SPF record points to an insufficiently strict SPF policy or a non-" "existing SPF record." +# TLS-RPT +msgid "detail mail auth tlsrpt exp" +msgstr "" +"We check if your domain has a TLS-RPT record. A receiving mail server can use the addresses in your TLS record to TODO\n" +"\n" +"For a \"good practice on domains without mail\" see the [explanation of the \"DMARC policy\" subtest](#control-panel-9)." + +msgid "detail mail auth tlsrpt label" +msgstr "TLS-RPT existence" + +msgid "detail mail auth tlsrpt tech table" +msgstr "TLS-RPT record" + +msgid "detail mail auth tlsrpt verdict bad" +msgstr "Your domain does *not* have a TLS-RPS record." + +msgid "detail mail auth tlsrpt verdict good" +msgstr "Your domain has a TLS-RPT record." + msgid "detail mail dnssec exists exp" msgstr "" "We check if your domain, more specifically its SOA record, is DNSSEC signed. With a DNSSEC signature senders who validate domain signatures can verify the authenticity of the DNS reply that contains your mail server domains (MX). This prevents an attacker from manipulating the DNS answer in order to redirect mails sent to you to the attacker's mailserver domain.\n" diff --git a/translations/nl/main.po b/translations/nl/main.po index 96d4406d2..06d1a4253 100644 --- a/translations/nl/main.po +++ b/translations/nl/main.po @@ -592,6 +592,26 @@ msgstr "" "record verwijst naar een onvoldoende strikte SPF-policy of naar een niet-" "bestaand SPF-record." +# TLS-RPT +msgid "detail mail auth tlsrpt exp" +msgstr "" +"We check if your domain has a TLS-RPT record. A receiving mail server can use the address in your TLS-RPT record to TODO.\n" +"\n" +"For a \"good practice on domains without mail\" see the [explanation of the \"DMARC policy\" subtest](#control-panel-9)." + +msgid "detail mail auth tlsrpt label" +msgstr "TLS-RPT aanwezigheid" + +msgid "detail mail auth tlsrpt tech table" +msgstr "TLS-RPT-record" + +msgid "detail mail auth tlsrpt verdict bad" +msgstr "Je domeinnaam heeft geen geldig TLS-RPT-record." + +msgid "detail mail auth tlsrpt verdict good" +msgstr "Je domein heeft een TLS-RPT-record." + + msgid "detail mail dnssec exists exp" msgstr "" "We testen of de domeinnaam in je e-mailadres, meer specifiek het SOA-record, ondertekend is met DNSSEC. De handtekening zorgt ervoor dat een verzender, die domeinhandtekeningen controleert, op een betrouwbare wijze jouw mailserverdomeinen (MX) kan opvragen. Dit voorkomt dat een aanvaller het antwoord manipuleert en aan jou gerichte mail omleidt naar een mailserverdomein dat onder controle is van de aanvaller.\n"