diff --git a/managed-services/transactional-email/how-to/add-dmarc-record.mdx b/managed-services/transactional-email/how-to/add-dmarc-record.mdx index 62391f2dc0..f3ea98d4af 100644 --- a/managed-services/transactional-email/how-to/add-dmarc-record.mdx +++ b/managed-services/transactional-email/how-to/add-dmarc-record.mdx @@ -53,9 +53,6 @@ To complete the actions presented below, you must have: 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; rua=mailto:df3bf92d-41ef-48b8-b6b0-b9a7659b2f58@dmarc.scw-tem.cloud; ruf=mailto:df3bf92d-41ef-48b8-b6b0-b9a7659b2f58@dmarc.scw-tem.cloud + v=DMARC1; p=none; ``` - - You may notice the `dmarc.scw-tem.cloud` part in the `rua` and `ruf` values. This is the Transactional Email's email address used to analyze your DMARC record and provide you with clearer metrics. - 6. Confirm the changes and add the DMARC record. \ No newline at end of file diff --git a/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx b/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx index bfeedca6db..f17f4ddf2f 100644 --- a/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx +++ b/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx @@ -49,7 +49,7 @@ Setting up an [MX record](/managed-services/transactional-email/concepts/#mx-rec Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. -4. Enter `blackhole.scw-tem.cloud.` in the **Hostname** field. Make sure you add the trailing dot at the end of the value. +4. Enter `blackhole.tem.scaleway.com.` in the **Hostname** field. Make sure you add the trailing dot at the end of the value. 5. Save your changes. diff --git a/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx b/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx index ca785e0393..8e0ecc7225 100644 --- a/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx +++ b/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx @@ -28,8 +28,8 @@ After you have configured your domain with Transactional Email, you are prompted 2. Click your domain. You are redirected to the SPF, DKIM and MX configuration page. 3. Copy the value that applies to your case to add an SPF record. - - If you have no SPF record on this domain, copy the following value: `v=spf1 include:_spf.scw-tem.cloud -all` - - If you already have configured an SPF record, copy the following value: `include:_spf.scw-tem.cloud` + - If you have no SPF record on this domain, copy the following value: `v=spf1 include:_spf.tem.scaleway.com/ -all` + - If you already have configured an SPF record, copy the following value: `include:_spf.tem.scaleway.com/` 4. Add a `TXT` record type in the root zone of your domain on your DNS zone. diff --git a/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx b/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx index f841d97a89..21458f2e18 100644 --- a/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx +++ b/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx @@ -80,7 +80,7 @@ The following output should display: Scaleway supports the `PLAIN` and `LOGIN` authentication methods. -The Transactional Email SMTP relay is available at `smtp.tem.scw.cloud` on ports `25`, `587`, `2587` (non TLS), `465` and `2465` (TLS). To send your emails using SMTP, a valid API secret key and your Project ID are required. +The Transactional Email SMTP relay is available at `smtp.tem.scaleway.com` on ports `25`, `587`, `2587` (non TLS), `465` and `2465` (TLS). To send your emails using SMTP, a valid API secret key and your Project ID are required. 1. [Generate an API key](/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam#generate-an-api-key-using-iam-and-send-emails-via-the-api) as shown above. 2. Authenticate yourself to the server using your Project ID as a username. diff --git a/managed-services/transactional-email/quickstart.mdx b/managed-services/transactional-email/quickstart.mdx index 98ef9658ee..a0eae31eb5 100644 --- a/managed-services/transactional-email/quickstart.mdx +++ b/managed-services/transactional-email/quickstart.mdx @@ -43,8 +43,8 @@ After you have configured your domain with Transactional Email, you are prompted 2. Click your domain. You are redirected to the SPF, DKIM and MX configuration page. 3. Copy the value that applies to your case to add an SPF record. - - If you have no SPF record on this domain, copy the following value: `v=spf1 include:_spf.scw-tem.cloud -all` - - If you already have configured an SPF record, copy the following value: `include:_spf.scw-tem.cloud` + - If you have no SPF record on this domain, copy the following value: `v=spf1 include:_spf.tem.scaleway.com/ -all` + - If you already have configured an SPF record, copy the following value: `include:_spf.tem.scaleway.com/` 4. Add a `TXT` record type in the root zone of your domain on your DNS zone. diff --git a/managed-services/transactional-email/reference-content/dmarc-configuration.mdx b/managed-services/transactional-email/reference-content/dmarc-configuration.mdx index a2e7b48fdb..a61b3fa552 100644 --- a/managed-services/transactional-email/reference-content/dmarc-configuration.mdx +++ b/managed-services/transactional-email/reference-content/dmarc-configuration.mdx @@ -60,9 +60,6 @@ There are two main types of DMARC reports: - aggregate reports (`rua`): aggregate reports provide data about a domain's email authentication activity. These reports include information such as the volume of emails received, the percentage of emails that pass or fail DMARC checks, and the sources of failed authentication. - forensic reports (`ruf`): forensic reports provide detailed information about individual email messages that fail DMARC authentication. They include the complete headers and body of the failed emails, details of the authentication checks performed, and any errors encountered. - - When configuring the Transactional Email DMARC record, you may notice `dmarc.scw-tem.cloud` in the `rua` and `ruf` values. This is the Transactional Email's email address used to analyze your DMARC record and provide you with clearer metrics. - | Tag | Description | Mandatory | Values expected | Default value | |---------|--------------------------------------------------------------------------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| diff --git a/managed-services/transactional-email/reference-content/smtp-configuration.mdx b/managed-services/transactional-email/reference-content/smtp-configuration.mdx index 1980876956..8a2b0be1a2 100644 --- a/managed-services/transactional-email/reference-content/smtp-configuration.mdx +++ b/managed-services/transactional-email/reference-content/smtp-configuration.mdx @@ -19,7 +19,7 @@ On this page, we go through different elements you might find in a standard SMTP ## Standard settings -1 - **SMTP Server Address (Host)** - The domain name or IP address of the SMTP server. If you are using Scaleway Transactional Email, the domain to use is `smtp.tem.scw.cloud`. +1 - **SMTP Server Address (Host)** - The domain name or IP address of the SMTP server. If you are using Scaleway Transactional Email, the domain to use is `smtp.tem.scaleway.com`. 2 - **SMTP Port** - The port number used to connect to the SMTP server. At Scaleway, the default ports are `25`, `587`, and `2587`.