From 0f439dbc5be49e67358705e507255ffbc390cc0c Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 11:59:11 -0600 Subject: [PATCH 1/6] DMARC regenerated in admin dash (what about cli?) --- docs/setup.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/setup.rst b/docs/setup.rst index eb79a697..df387c51 100644 --- a/docs/setup.rst +++ b/docs/setup.rst @@ -61,6 +61,10 @@ Perform the specific setup steps Specific setup steps are described per flavor (Compose, Kubernetes, etc.) and you should follow the steps after completing the requirements. +After setting up your flavor, continue to the DNS setup instructions, +additional steps in the admin dashboard will be needed to generate your +DMARC and SPF/DKIM keys. + Make sure that you test properly before going live! - Try to send an email to an external service From 5fe7fb4bf8a71ba1f42f8fdd3eb7f27aaf160755 Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 12:06:39 -0600 Subject: [PATCH 2/6] location in the admin UI to regenerate DMARC/SPF/DKIM --- docs/dns.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/dns.rst b/docs/dns.rst index d2fd4131..a96383b6 100644 --- a/docs/dns.rst +++ b/docs/dns.rst @@ -48,3 +48,13 @@ And for another domain, ``myotherdomain.com`` for example: myotherdomain.com. IN MX 10 mail.mydomain.com. Note that both point to the same mail server hostname, which is unique to your server. + +DKIM/SPF & DMARC Entries +------------------------ + +Finally, you'll need to visit the admin dashboard (or use the cli) to regenerate your DMARC, SPF, and DKIM records. + +Once the DNS changes to your host have propogated (and if SSL / domain rules were setup correctly, visit your admin +dashboard at https://example.com/admin/ui/domain/details/example.com. Click on `regenerate keys` and add the required +records to your DNS provider. If you've enabled DKIM/SPF / DMARC and haven't added these entries, your mail might +not get delivered. From 55224fb915904cb588c4752721e042a6e1f7c4b3 Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 12:11:01 -0600 Subject: [PATCH 3/6] suggestion on fixing some access denied errors for admin. --- docs/faq.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 9d69f2c5..280a8d42 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -319,6 +319,11 @@ down and up again. A container restart is not sufficient. *Issue reference:* `615`_. +Access Denied Errors +-------------------- + +While this may be due to several issues, check to make sure your ``DOMAIN=`` entry is the **first** entry in your ``HOSTNAMES=``. + TLS certificate issues `````````````````````` From f1eb2ee3676eda4041f05b746e063b12cdeda7c5 Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 12:19:06 -0600 Subject: [PATCH 4/6] solve admin problems by recommending it in setup, not just FAQ. --- setup/templates/steps/compose/03_expose.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/setup/templates/steps/compose/03_expose.html b/setup/templates/steps/compose/03_expose.html index c909fc9b..291ea672 100644 --- a/setup/templates/steps/compose/03_expose.html +++ b/setup/templates/steps/compose/03_expose.html @@ -50,7 +50,9 @@ avoid generic all-interfaces addresses like 0.0.0.0 or ::You server will be available under a main hostname but may expose multiple public hostnames. Every e-mail domain that points to this server must have one of the -hostnames in its MX record. Hostnames must be coma-separated.

+hostnames in its MX record. Hostnames must be coma-separated. If you're having +trouble accessing your admin interface, make sure it is the first entry here (and possibly the +same as your DOMAIN entry from earlier.

From ca5e0c88ba56bbefbae74334305b3f377a330c73 Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 12:19:38 -0600 Subject: [PATCH 5/6] update in stack, as well. --- setup/templates/steps/stack/03_expose.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/setup/templates/steps/stack/03_expose.html b/setup/templates/steps/stack/03_expose.html index 5377d3bd..c5daa24d 100644 --- a/setup/templates/steps/stack/03_expose.html +++ b/setup/templates/steps/stack/03_expose.html @@ -11,7 +11,9 @@ you expose it to the world.

You server will be available under a main hostname but may expose multiple public hostnames. Every e-mail domain that points to this server must have one of the -hostnames in its MX record. Hostnames must be coma-separated.

+hostnames in its MX record. Hostnames must be coma-separated. If you're having +trouble accessing your admin interface, make sure it is the first entry here (and possibly the +same as your DOMAIN entry from earlier.

From 6ca59f20b52418fe0dff91427a06ae1bb611e53d Mon Sep 17 00:00:00 2001 From: toxik-io Date: Tue, 7 May 2019 12:29:24 -0600 Subject: [PATCH 6/6] typo. --- docs/dns.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dns.rst b/docs/dns.rst index a96383b6..027ce4fc 100644 --- a/docs/dns.rst +++ b/docs/dns.rst @@ -54,7 +54,7 @@ DKIM/SPF & DMARC Entries Finally, you'll need to visit the admin dashboard (or use the cli) to regenerate your DMARC, SPF, and DKIM records. -Once the DNS changes to your host have propogated (and if SSL / domain rules were setup correctly, visit your admin +Once the DNS changes to your host have propogated (and if SSL / domain rules were setup correctly), visit your admin dashboard at https://example.com/admin/ui/domain/details/example.com. Click on `regenerate keys` and add the required records to your DNS provider. If you've enabled DKIM/SPF / DMARC and haven't added these entries, your mail might not get delivered.