Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • Mailman Core Mailman Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 354
    • Issues 354
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 56
    • Merge requests 56
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNU Mailman
  • Mailman CoreMailman Core
  • Issues
  • #343
Closed
Open
Created Jun 08, 2017 by Aurélien Bompard@abompardOwner

Bounce events are never processed

Mailman stores a bounce event in the database when it happens. Is there any good reason to keep them there indefinitely? On the production Fedora install this table is now 13 million rows large, so I have two questions:

  • Is it used for anything else than logging, and if no is it self to expunge?
  • Should we setup a periodic expiration of those entries?
Edited Jun 09, 2017 by Barry Warsaw
Assignee
Assign to
Time tracking