瀏覽代碼

Update docs/configuring-playbook-email.md: minor edit

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

+ 1
- 1
docs/configuring-playbook-email.md 查看文件

@@ -31,7 +31,7 @@ By default, exim-relay attempts to deliver emails directly. This may or may not

To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers.

For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's document.
For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation.

💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server.



Loading…
取消
儲存