github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 07:41:34 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:41:34 -06:00
Owner
Copy Link

Originally created by @mxmehl on GitHub (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

Originally created by @mxmehl on GitHub (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_
GiteaMirror commented 2025-11-02 07:41:35 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (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.

@KN4CK3R commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7920
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?