feat(tem): merge pages #5606

ldecarvalho-doc · 2025-10-01T15:40:59Z

No description provided.

jerjako · 2025-10-01T16:14:52Z

pages/transactional-email/how-to/authenticate-domain.mdx

+9. Add an [MX record](/transactional-email/how-to/add-mx-record-to-your-domain/).
+10. Check the box "I have added these DNS records to my DNS zone" to confirm.
+11. Click **Verify domain**. Your domain displays in the list of your domains.


the lines 9, 10 and 11 should be in a separate last section or just removed

jerjako · 2025-10-01T16:17:28Z

pages/transactional-email/how-to/authenticate-domain.mdx

+  - **DMARC record** – Defines how receiving servers should handle authentication failures and enables reporting for your domain.
+  - **MX record** – Directs incoming emails to your mail server but is not involved in sending or authenticating outgoing emails.
+
+## How to configure SPF and DKIM records


Having SPF and DKIM in one section. And DMARC in another could be improved.

SPF need some "logic" (add an include in the right place)

DMARC needs also some logic

But DKIM is just a copy / paste in a unique dns record name.

Separate all of them may help people in case of error on one particular record

jerjako · 2025-10-01T16:19:15Z

pages/transactional-email/how-to/authenticate-domain.mdx

+### How to configure Scaleway's DMARC record
+
+1. Access your domain's **DNS Verification** tab and scroll down to the **DMARC record** section.
+2. Copy the values that display in the **Name** and the **Value** fields.
+3. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone.
+4. In the **Name** field, paste the value you have copied in step 2, followed by the domain name.
+5. In the **Value** field, paste the value you have copied in step 2. Your **Value** field should look like the following:
+    ```
+    v=DMARC1; p=none;
+    ```
+6. Confirm the changes and add the DMARC record.


IMO, this 2nd section of the same title "How to configure Scaleway's DMARC record" could be removed

RoRoJ · 2025-10-02T09:31:37Z

pages/transactional-email/how-to/authenticate-domain.mdx

+    v=DMARC1; p=none; rua=mailto:[email protected]
+    ```
+    <Message type="important">
+     It is possible to configure several DMARC records for one domain, but they must have a different name to be valid.


Suggested change

It is possible to configure several DMARC records for one domain, but they must have a different name to be valid.

It is possible to configure several DMARC records for one domain, but they must have different names to be valid.

RoRoJ · 2025-10-02T09:32:02Z

pages/transactional-email/how-to/authenticate-domain.mdx

+1. Access your domain's **DNS Verification** tab and scroll down to the **DMARC record** section.
+2. Copy the values that display in the **Name** and the **Value** fields.
+3. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone.
+4. In the **Name** field, paste the value you have copied in step 2, followed by the domain name.


Suggested change

4. In the **Name** field, paste the value you have copied in step 2, followed by the domain name.

4. In the **Name** field, paste the value you copied in step 2, followed by the domain name.

RoRoJ · 2025-10-02T09:32:09Z

pages/transactional-email/how-to/authenticate-domain.mdx

+2. Copy the values that display in the **Name** and the **Value** fields.
+3. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone.
+4. In the **Name** field, paste the value you have copied in step 2, followed by the domain name.
+5. In the **Value** field, paste the value you have copied in step 2. Your **Value** field should look like the following:


Suggested change

5. In the **Value** field, paste the value you have copied in step 2. Your **Value** field should look like the following:

5. In the **Value** field, paste the value you copied in step 2. Your **Value** field should look like the following:

RoRoJ · 2025-10-02T09:32:34Z

pages/transactional-email/how-to/authenticate-domain.mdx

+## How to configure MX records
+
+<Message type="important">
+  We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX, will be lost and unrecoverable.


Suggested change

We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX, will be lost and unrecoverable.

We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX will be lost and unrecoverable.

RoRoJ · 2025-10-02T09:33:02Z

pages/transactional-email/how-to/authenticate-domain.mdx

+### How to add Scaleway's MX record
+
+<Message type="important">
+  - Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a **blackhole**. This means that **any email sent back to it, will be lost with no possibility of recovery**.


Suggested change

- Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a **blackhole**. This means that **any email sent back to it, will be lost with no possibility of recovery**.

- Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a **blackhole**. This means that **any email sent back to it will be lost with no possibility of recovery**.

jcirinosclwy · 2025-10-02T14:14:41Z

pages/transactional-email/how-to/authenticate-domain.mdx

+2. Click the name of the email domain you want to authenticate. The domain overview page displays. You can see the status of the DNS records.
+3. Click the **DNS records** tab.
+
+On this tab you can configure:


Suggested change

On this tab you can configure:

On this tab, you can configure:

jcirinosclwy · 2025-10-02T14:15:55Z

pages/transactional-email/how-to/authenticate-domain.mdx

+
+3. Add a `TXT` record type in the root zone of your domain on your DNS zone.
+4. Paste the value you have copied in the root zone of your domain.
+5. Add an additional `TXT` record type in the root zone of your domain on your DNS zone.


Suggested change

5. Add an additional `TXT` record type in the root zone of your domain on your DNS zone.

5. Add another `TXT` record type in the root zone of your domain on your DNS zone.

jcirinosclwy · 2025-10-02T14:17:32Z

pages/transactional-email/how-to/authenticate-domain.mdx

+1. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone.
+2. Enter `_dmarc` in the **Name** field, followed by the domain name. For example, if your domain is called `my-domain.com`, you should have `_dmarc.my-domain.com.` in the **Name** field.
+3. Enter your desired tags and their values in the **Value** section. Make sure that you add the mandatory `v` and `p` tags, and that you separate tags from each other with semi-colons. Find out about DMARC configuration in our [dedicated documentation](/transactional-email/reference-content/dmarc-configuration/).
+    Your **Value** field should look similar to the following


Suggested change

Your **Value** field should look similar to the following

Your **Value** field should look similar to the following:

jcirinosclwy · 2025-10-02T14:17:54Z

pages/transactional-email/how-to/authenticate-domain.mdx

+     It is possible to configure several DMARC records for one domain, but they must have a different name to be valid.
+     For example, the `_dmarc.mydomain.com` and `_dmarc.tem.mydomain.com` DMARC records are valid.
+    </Message>
+6. Confirm the changes and add the DMARC record.


Suggested change

6. Confirm the changes and add the DMARC record.

4. Confirm the changes and add the DMARC record.

jcirinosclwy · 2025-10-02T14:19:01Z

pages/transactional-email/how-to/authenticate-domain.mdx

+
+

Suggested change

feat(tem): merge pages

8af02ac

ldecarvalho-doc self-assigned this Oct 1, 2025

feat(tem): fix impory

7a2ba24

jerjako reviewed Oct 1, 2025

View reviewed changes

RoRoJ approved these changes Oct 2, 2025

View reviewed changes

jcirinosclwy reviewed Oct 2, 2025

View reviewed changes

pages/transactional-email/how-to/authenticate-domain.mdx

Comment on lines +127 to +128

Copy link

Collaborator

jcirinosclwy Oct 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

jcirinosclwy approved these changes Oct 2, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(tem): merge pages #5606

feat(tem): merge pages #5606

Uh oh!

ldecarvalho-doc commented Oct 1, 2025

Uh oh!

jerjako Oct 1, 2025

Uh oh!

jerjako Oct 1, 2025

Uh oh!

jerjako Oct 1, 2025

Uh oh!

RoRoJ Oct 2, 2025

Uh oh!

RoRoJ Oct 2, 2025

Uh oh!

RoRoJ Oct 2, 2025

Uh oh!

RoRoJ Oct 2, 2025

Uh oh!

RoRoJ Oct 2, 2025

Uh oh!

jcirinosclwy Oct 2, 2025

Uh oh!

jcirinosclwy Oct 2, 2025

Uh oh!

jcirinosclwy Oct 2, 2025

Uh oh!

jcirinosclwy Oct 2, 2025

Uh oh!

jcirinosclwy Oct 2, 2025

Uh oh!

Uh oh!

	It is possible to configure several DMARC records for one domain, but they must have a different name to be valid.
	It is possible to configure several DMARC records for one domain, but they must have different names to be valid.

	4. In the Name field, paste the value you have copied in step 2, followed by the domain name.
	4. In the Name field, paste the value you copied in step 2, followed by the domain name.

	5. In the Value field, paste the value you have copied in step 2. Your Value field should look like the following:
	5. In the Value field, paste the value you copied in step 2. Your Value field should look like the following:

	We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX, will be lost and unrecoverable.
	We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX will be lost and unrecoverable.

	- Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a blackhole. This means that any email sent back to it, will be lost with no possibility of recovery.
	- Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a blackhole. This means that any email sent back to it will be lost with no possibility of recovery.

	On this tab you can configure:
	On this tab, you can configure:

	5. Add an additional `TXT` record type in the root zone of your domain on your DNS zone.
	5. Add another `TXT` record type in the root zone of your domain on your DNS zone.

	Your Value field should look similar to the following
	Your Value field should look similar to the following:

	6. Confirm the changes and add the DMARC record.
	4. Confirm the changes and add the DMARC record.

feat(tem): merge pages #5606

Are you sure you want to change the base?

feat(tem): merge pages #5606

Uh oh!

Conversation

ldecarvalho-doc commented Oct 1, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!