-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Threaded email notifications by adding missing mail headers #2645
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
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
can message IDs be anything or do they need to confirm to a specific format? |
Basically this is quite free to define accoridng to RFC 2392 as long as every ID is globally unique. But in order to enable the tree structure, it should follow a certain form. Github seems to do it as follows:
As you can see, no need to create new random strings, as the Gitea domain, the user/repo name, the pull/issue number, and the comment ID will make every Message-ID unique. The missing Message-ID also causes Gitea's mails to be caught by more and more spam filters. |
Closed by #7484 as it seems. Thanks @mrsdizzie ! |
Description
Currently, the email notifications lack some headers which would make them easier to read and follow in mail clients. Even in a modern MUA the notification mails aren't shown in a thread like with Github mails.
This is because following headers are missing (from a mail of a Github pull request):
Message-ID: <astroidmail/astroid/pull/412/push/2025975904@github.com>
In-Reply-To: <astroidmail/astroid/pull/412@github.com>
References: <astroidmail/astroid/pull/412@github.com>
While the message-id isn't required to allow the threaded view it's part of a valid email layout.
The text was updated successfully, but these errors were encountered: