We have clarified our Privacy Statement even further. Please have a look at our changes.

#95 message-id field on emails non-unique

Open
opened 1 week ago by libBletchley · 1 comments

Expected behavior

Every single email should have a unique Message-Id: header field.

Actual behavior

The email announcing the opening and closure of an issue uses the same msg id. E.g., this is the msg id for the opening and closing of bug 16 of the cloudflare-tor repo:

Message-ID: <crimeflare/cloudflare-tor/issues/16@codeberg.org>

Impact

Mail tools rely on unique message IDs for a variety of functions such as detecting duplicate messages. A common Procmail recipe deletes dupes by comparing the message ID to a cache of seen message IDs. Mutt signals that a message is a dupe with an “=” symbol, and is falsely flagging the closure messages as dupes.

# Expected behavior Every single email should have a unique `Message-Id:` header field. # Actual behavior The email announcing the opening and closure of an issue uses the same msg id. E.g., this is the msg id for the opening and closing of bug 16 of the cloudflare-tor repo: `Message-ID: <crimeflare/cloudflare-tor/issues/16@codeberg.org>` # Impact Mail tools rely on unique message IDs for a variety of functions such as detecting duplicate messages. A common Procmail recipe deletes dupes by comparing the message ID to a cache of seen message IDs. Mutt signals that a message is a dupe with an "=" symbol, and is falsely flagging the closure messages as dupes.
ashimokawa commented 1 week ago
Owner

Good point. Thanks for reporting!

Good point. Thanks for reporting!
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.