Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Register
  • Sign in
  • F foodsharing
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 359
    • Issues 359
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • foodsharing-devfoodsharing-dev
  • foodsharing
  • Issues
  • #886
Closed
Open
Issue created Apr 24, 2020 by Johannes@jofranzReporter

Implement a better way for email rate limiting to double our current sending rate

Our mail sponsor asks us, to rate limit our email sending to 1.000 mails in 10 minutes. We only reach this when sending newsletter or if there are very high peaks. This is the positive thing of this.
Our current implementation only allows us to send not even half of this.

Details can be read in our developer@foodsharing.network inbox:

"Re: Mögliche Email rate limits besser verstehen – Kunde 23955" (24.03.2020)

Current rate limiting in postfix only allows us to theoretically 60 mails per second which turns out to only be ~47 in reality as you can see here. The delay between mails of this limit only can be set higher :/

With !1419 (merged) there is a rate limit in php active which might not be the best solution. I implemented it, as I didn't get much help. It can make sense to keep it as Postfix seems to not send mails in first-in first-out manner when there is a large queue over 10k or 20k. Currently there is a low limit active.
!1419 (diffs)

A dragondreaming implementation of this would be a prioritisation system which allows giving newsletter and infomail stuff a very low prio while chat, store, foodsharepoint and forum mails have a higher prio.

Assignee
Assign to
Time tracking