foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-12-23 22:20:43 -05:00
Code Issues Activity

incoming-email.md: s/gitea/forgejo/

Browse source
This commit is contained in:
Loïc Dachary 2023-02-27 01:21:54 +01:00
parent 4cdb35ae5f
commit 45c01dfb47
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
admin/incoming-email.md
View file

@ -3,7 +3,7 @@ layout: '~/layouts/Markdown.astro'
title: 'Incoming Email'
---
Gitea supports the execution of several actions through incoming mails. This page describes how to set this up.
Forgejo supports the execution of several actions through incoming mails. This page describes how to set this up.
**Table of Contents**
@ -13,10 +13,10 @@ Gitea supports the execution of several actions through incoming mails. This pag
Handling incoming email messages requires an IMAP-enabled email account.
The recommended strategy is to use [email sub-addressing](https://en.wikipedia.org/wiki/Email_address#Sub-addressing) but a catch-all mailbox does work too.
The receiving email address contains a user/action specific token which tells Gitea which action should be performed.
The receiving email address contains a user/action specific token which tells Forgejo which action should be performed.
This token is expected in the `To` and `Delivered-To` header fields.
Gitea tries to detect automatic responses to skip and the email server should be configured to reduce the incoming noise too (spam, newsletter).
Forgejo tries to detect automatic responses to skip and the email server should be configured to reduce the incoming noise too (spam, newsletter).
## Configuration