-
Notifications
You must be signed in to change notification settings - Fork 258
feat(tem): blocklist - MTA-5412 #4250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
3126bbf
fix(tem): blocklist draft
ldecarvalho-doc 845e3e1
fix(tem): blocklist draft 2
ldecarvalho-doc 98034d3
fix(tem): doc blocklist
ldecarvalho-doc 28694e0
fix(tem): add to menu
ldecarvalho-doc a12b079
fix(tem): concept
ldecarvalho-doc a18b5e5
fix(tem): remove question from faq
ldecarvalho-doc 1882676
fix(tem): add webhooks and permission sets
ldecarvalho-doc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
37 changes: 37 additions & 0 deletions
37
managed-databases/postgresql-and-mysql/troubleshooting/database-unavailable.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| --- | ||
| meta: | ||
| title: My Database Instance is unavailable | ||
| description: Troubleshoot extension errors for PostgreSQL databases. | ||
| content: | ||
| h1: My Database Instance is unavailable | ||
| paragraph: Troubleshoot extension errors for PostgreSQL databases. | ||
| tags: disk-full databases | ||
| dates: | ||
| validation: 2025-01-20 | ||
| posted: 2025-01-20 | ||
| categories: | ||
| - managed-databases | ||
| - postgresql-and-mysql | ||
| --- | ||
|
|
||
|
|
||
| ## Backup restoration error | ||
|
|
||
| ### Problem | ||
|
|
||
| The following error appears when restoring a database from a logical backup: | ||
| ``` | ||
| pg_restore: while PROCESSING TOC: pg_restore: ... pg_restore: error: could not execute query: ERROR: function unaccent(character varying) does not exist | ||
| ``` | ||
|
|
||
| ### Cause | ||
|
|
||
| The `unaccent` extension is installed in a public schema, the `search_path` is not set to public, and the namespace was not defined when running the function. | ||
|
|
||
| ### Solution | ||
|
|
||
| For security reasons only the `pg_catalog` namespace is checked during backup restoration. Therefore you must check in which namespace the faulty function is defined. The function should be defined with an explicit namespace when it is used. | ||
|
|
||
| Run the function again while defining the namespace. | ||
|
|
||
| For more information and examples refer to the [PostgreSQL extensions reference](/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions) page. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
55 changes: 55 additions & 0 deletions
55
managed-services/transactional-email/how-to/manage-blocklists.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| --- | ||
| meta: | ||
| title: How to manage Transactional Email blocklists | ||
| description: This page provides instructions how to improve the quality of your email deliveries and maintain your domain's reputation score with TEM blocklists. | ||
| content: | ||
| h1: How to manage Transactional Email blocklists | ||
| paragraph: This page provides instructions how to improve the quality of your email deliveries and maintain your domain's reputation score with TEM blocklists. | ||
| tags: blocklist reputation transactional | ||
| dates: | ||
| validation: 2025-01-20 | ||
| posted: 2025-01-20 | ||
| categories: | ||
| - managed-services | ||
| --- | ||
|
|
||
| The Transactional Email blocklist feature allows your to manage email addresses that generate errors, or “bounces”. This helps you improve the quality of your email deliveries, maintain your domain's reputation score, and reduce the risk of having your domains blocked by ISPs. | ||
|
|
||
| <Macro id="requirements" /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - [Configured your domain(s) with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) | ||
|
|
||
| ## How to monitor temporary blocklists | ||
|
|
||
| If any of your emails were bounced, you will see a temporary blocklist entry, with a duration of 48h, containing the details of the email that bounced and the reason, or flag. Some examples of bounce reasons are: | ||
|
|
||
| - `Mailbox not found` - when mailbox does not exist | ||
| - `Mailbox full` - when the mailbox is full. | ||
|
|
||
| The temporary blocklist entry is created automatically to prevent repeated attempts to send e-mails, which could damage your reputation. | ||
|
|
||
| To see the blocklist: | ||
|
|
||
| 1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. Your domains display. | ||
| 2. Click the domain for which you want to manage the blocklist. An overview of your domain appears. | ||
| 3. Click the **Blocklist** tab. Your blocklist displays detailing the recipient email, the flags, the date the block began and when it ends. | ||
|
|
||
| ## How to unblock an email address | ||
|
|
||
| You can unblock any address that was added to the blocklist. This is useful in cases where: | ||
|
|
||
| - A temporary error has been corrected. The recipient has freed up space in their mailbox, for example. | ||
| - An address becomes valid again after an update. | ||
|
|
||
| 1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. Your domains display. | ||
| 2. Click the domain for which you want to manage the blocklist. An overview of your domain appears. | ||
| 3. Click the **Blocklist** tab. Your blocklist displays. | ||
| 4. Click **Unblock** next to the email address you wish to unblock. A pop-up appears to warn you to: | ||
|
|
||
| <Message type="important"> | ||
| Make sure the issue causing the email's rejection is resolved before unblocking it to protect your reputation score and ensure optimal email deliverability. | ||
| </Message> | ||
| 5. Type **UNBLOCK** and click **Unblock** if you wish to continue. | ||
| The email address is removed from your blocklist. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.