Skip to content

Commit 5837fad

Browse files
docs(tem): changes
1 parent 2e93241 commit 5837fad

File tree

4 files changed

+26
-6
lines changed

4 files changed

+26
-6
lines changed

faq/transactional-email.mdx

+3-2
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,10 @@ Check out our [dedicated page](https://www.scaleway.com/en/pricing/?tags=managed
5757
Yes, you can manually unblock any address, even if it is still under the temporary block period. You can unblock up to five addresses every 24 hours.
5858

5959
## What happens if an address on a TEM blocklist becomes valid again?
60-
You can manually unblock the address. Make sure you confirm that the initial cause of the bounce was resolved before doing so to avoid further issues.
60+
You can manually unblock any addresses. Make sure you confirm that the initial cause of the bounce was resolved before doing so to avoid further issues.
6161

62-
Here's the translation:
62+
## Can I remove addresses from the blocklist?
63+
Yes, all blocked addresses can be unblocked via the interface. For addresses you added manually, you have full control over when and if they are removed from the blocklist.
6364

6465
## What are the main benefits of the Scale offer?
6566
The Scale offer provides advanced control over email deliverability through a dedicated IP, detailed performance tracking, and advanced webhook management. It is ideal for businesses with high email sending volume requirements.

pages/transactional-email/how-to/manage-blocklists.mdx

+14-1
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,27 @@ categories:
1313
- managed-services
1414
---
1515

16-
The Transactional Email blocklist feature allows your to manage email addresses that generate errors, or “bounces”. Emails are automatically blocked when a mailbox does not exist, or is full, to prevent sending emails to a recipient address that is not reachable.
16+
The Transactional Email (TEM) blocklist feature allows your to manage email addresses that generate errors, or “bounces”. Emails are automatically blocked when a mailbox does not exist, or is full, to prevent sending emails to a recipient address that is not reachable. You can also add emails to the blocklist manually if you subscribe to the [TEM Scale plan]() and have a Scaleway domain.
1717

1818
<Macro id="requirements" />
1919

2020
- A Scaleway account logged into the [console](https://console.scaleway.com)
2121
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization. For blocklists your can apply the `TransactionalEmailBlocklistFullAccess` permission
2222
- [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/)
2323

24+
## How to add an email address to the blocklist
25+
26+
You can manually add address to your blocklist in the Scaleway console. When you add an email to the blocklist, it remains blocked indefinitely until you decide to [unblock it](#how-to-unblock-an-email-adress).
27+
28+
<Message type="important">
29+
Manually adding an email address to a domain's blocklist is only available for users who have a Scaleway domain and subscribe to the [TEM Scale plan]() for that domain's Project.
30+
</Message>
31+
32+
1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. Your domains display.
33+
2. Click the domain for which you want to manage the blocklist. An overview of your domain appears.
34+
3. Click the **Blocklist** tab.
35+
4.
36+
2437
## How to monitor temporary blocklists
2538

2639
If any of your emails bounced, you will see a temporary blocklist entry, with a duration of 48 hours, containing the details of the email that bounced and the reason, or flag. Some examples of bounce reasons are:

pages/transactional-email/how-to/monitor-transactional-email-cockpit.mdx

+2-1
Original file line numberDiff line numberDiff line change
@@ -79,4 +79,5 @@ Metrics are refreshed every minute, and report on the following data:
7979
At the top of the dashboard, you can configure the following parameters, that control which metrics are displayed:
8080

8181
- **Datasource** - Select the SCW region for which you want to see the metrics.
82-
- **Domain** - Select the specific domain for which you want to see the metrics
82+
- **Domain** - Select the specific domain for which you want to see the metrics
83+
- **Timeframe** - Get metrics from the last five minutes up to 31 days (free plan) and 365 days (premium plan).

pages/transactional-email/reference-content/tem-dedicated-ip.mdx

+7-2
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The following dedicated IP management actions are included with the TEM [Scale p
2929
The Scaleway TEM team will intervene as much as possible to improve and maintain the domain's reputation score. However, since the TEM team does not own the domain, and has no control over traffic, they cannot commit to the complete resolution of incidents.
3030
</Message>
3131

32-
## When to Use a Dedicated IP?
32+
## When to use a dedicated IP?
3333

3434
Dedicated IPs are useful for managing:
3535

@@ -38,11 +38,16 @@ Dedicated IPs are useful for managing:
3838
- **Sensitive sends** - Cases such as financial transactions, healthcare, public, defense, or critical communications where confidentiality or reputation are crucial.
3939
- **Compliance and security** - Regulatory compliance and maintaining the security of your email sending infrastructure, including obtaining necessary certifications and whitelisting your email sending IPs.
4040

41-
## When is a Dedicated IP Not Necessary?
41+
## When is a dedicated IP not necessary?
4242

4343
A dedicated IP is not always advantageous, and in some cases, it can even harm deliverability:
4444

4545
- **Low volumes** - If you send less than 10,000 emails per month, a dedicated IP may struggle to maintain a good reputation.
4646
- **Irregular sends** - If your sending volumes are inconsistent, it can be difficult to stabilize the reputation of your IP.
4747
- **Poor emailing practices** - A dedicated IP does not improve deliverability if you have poor emailing practices (high bounce rates, spam complaints, etc.).
4848

49+
## Technical limitations
50+
51+
- When you activate a dedicated IP on a project, all emails from the Project will be sent via this IP.
52+
- It is not possible to use a shared and a dedicated IP on the same Project. This limitation is put in place to avoid routing and sending reputation inconsistencies. If you wish to use a shared IP for certain sends, you need to do so on a separate project.
53+
- Only the TEM team can make advanced adjustments to the IP in the event of major incidents.

0 commit comments

Comments
 (0)