瀏覽代碼

Update docs for DNS settings: Email2Matrix

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/3936/head
Suguru Hirahara 1 年之前
父節點
當前提交
ff6ef85d5e
沒有發現已知的金鑰在資料庫的簽署中 GPG 金鑰 ID: E4F9743DAB4B7B75
共有 1 個檔案被更改,包括 8 行新增4 行删除
  1. +8
    -4
      docs/configuring-playbook-email2matrix.md

+ 8
- 4
docs/configuring-playbook-email2matrix.md 查看文件

@@ -8,10 +8,6 @@ See the project's [documentation](https://github.com/devture/email2matrix/blob/m

## Preparation

## Adjusting DNS records

It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page.

### Port availability

Ensure that port 25 is available on your Matrix server and open in your firewall.
@@ -54,6 +50,14 @@ Make sure that you and the sender user are part of the same room and that the se

Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below.

## Adjusting DNS records

To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this:

| Type | Host | Priority | Weight | Port | Target |
|------|----------|----------|--------|------|------------------------------------|
| MX | `matrix` | 10 | 0 | - | `matrix.example.com` |

## Adjusting the playbook configuration

To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token).


Loading…
取消
儲存