Codeberg/Community
54
325
Fork
You've already forked Community
12

Emails are arriving out-of-order #2138

Closed
opened 2025年09月17日 17:03:21 +02:00 by untitaker · 2 comments

Comment

It seems that in some issue conversations where there is a message every 5-10 minutes, codeberg is sending out the notification emails both with a delay and in the wrong order.

The Date header seems correct, but Received is out of order.

On FastMail I believe there is no way to sort messages according to Date: https://www.fastmail.com/blog/default-sort-order-changed-to-received-date/

I mean, this is obviously not something Codeberg has to fix, I'm just wondering: Have other folks who use FastMail found a workaround for this issue?

Curiously I have never had this issue on GitHub even though they definitely had delivery delays. I wonder if they send mails in-order per-thread.

### Comment It seems that in some issue conversations where there is a message every 5-10 minutes, codeberg is sending out the notification emails both with a delay and in the wrong order. The `Date` header seems correct, but `Received` is out of order. On FastMail I believe there is no way to sort messages according to `Date`: https://www.fastmail.com/blog/default-sort-order-changed-to-received-date/ I mean, this is obviously not something Codeberg has to fix, I'm just wondering: Have other folks who use FastMail found a workaround for this issue? Curiously I have never had this issue on GitHub even though they definitely had delivery delays. I wonder if they send mails in-order per-thread.
Owner
Copy link

We are delaying notifications coming from new users to increase chances the mails can be caught in delivery, should they be reported as spam. I suppose this leads to the issues.

The blog post you shared goes into detail about how to configure this. I suppose you just need to follow it?

We are delaying notifications coming from new users to increase chances the mails can be caught in delivery, should they be reported as spam. I suppose this leads to the issues. The blog post you shared goes into detail about how to configure this. I suppose you just need to follow it?

no, this was a conversation between codeberg members with very old accounts. all emails during that time were delayed irrespective of user. the blog post is out of date, these options don't exist anymore. either way I suppose there is nothing to do

no, this was a conversation between codeberg members with very old accounts. all emails during that time were delayed irrespective of user. the blog post is out of date, these options don't exist anymore. either way I suppose there is nothing to do
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2138
Reference in a new issue
Codeberg/Community
No description provided.
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?