Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • concrexit concrexit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • thalia
  • concrexitconcrexit
  • Issues
  • #844

Closed
Open
Created Apr 01, 2019 by Sébastiaan Versteeg@sversteegOwner

Re-implement the way we handle mailinglist aliases

One-sentence description

Re-implement the way we handle mailinglist aliases

Why?

Decrease workload on server

Current implementation

All aliases are handled as separate mailinglists and synced like so. If an email gets sent to an alias of a mailinglist the message doesn't end up in the main mailinglist archive.

Suggested implementation

The alias should redirect incoming email to the main mailinglist without additions or archiving. This should speed up the syncing of mailinglists as well.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking