Skip to content

Message-ID header missing in follow-up email notifications #17203

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
mxmehl opened this issue Oct 1, 2021 · 1 comment · Fixed by #17206
Closed

Message-ID header missing in follow-up email notifications #17203

mxmehl opened this issue Oct 1, 2021 · 1 comment · Fixed by #17206

Comments

@mxmehl
Copy link

mxmehl commented Oct 1, 2021

Gitea Version

1.15.3

Git Version

2.30.2

Operating System

Debian 10

How are you running Gitea?

Binary packages running via systemd

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Description

The first notification mail of an issue or pull request contains a valid Message-ID header, e.g. Message-ID: <fsfe-system-hackers/baseline/issues/10@git.fsfe.org>.

However, all following mails do not carry this header for some reason. This is bad because it does not conform with RFC 5322, and spam filters often downrate it or even not not let it pass (in RSPAMD: MISSING_MID(2.5)).

Not sure whether it relates to #13065.

Screenshots

No response

@KN4CK3R
Copy link
Member

KN4CK3R commented Oct 1, 2021

However, all following mails do not carry this header for some reason.

The reason is the comment
// Set Message-ID on first message so replies know what to reference
but that's wrong. Will be fixed with #17206.

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants