Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
schleuder
schleuder
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 101
    • Issues 101
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • schleuder
  • schleuderschleuder
  • Issues
  • #364

Closed
Open
Opened Jul 19, 2018 by init void@init

Admin will self-unsubscribe with accidental line-break in x-unsubscribe:-command

One of our list-admins send the following request:

x-list-name: some-list@listserver.net
x-unsubscribe:
mail@example.net

I don't know, why he added a line break? Users to these things. Admin was removed. List stoped working immediately, due to missing admin. Admin had to be restored by schleuder-cli.

Expected Behavior

The command should complain that the subscription-e-mail is missing. or The admin should get a warning, that he is about to unsubscribe himself and some confirmation like force is required.

Actual Behavior

Since the command does not get an e-mail-address on the same line, it assumes that the sender wants to unsubscribe himself.

Steps to Reproduce the Problem

  1. Be Admin
  2. Try to unsubscribe a list member
  3. Add a line-break between x-unsubscribe: and the e-mail-address.

Specifications

  • Version: 3.2.2-1~bpo9+1
  • Installation method: deb
  • Mail client version: any

Other information

I see, why the current behavior is useful. A person that want's to get off the list just sends x-unsubscribe: . Done.

But I'm filing this issue anyway because we had the problem with an actual admin. The list shutting down because of the unsubscribed admin caused some stress for the group using the list.

So, the command behaves as intended.
But this intended behavior bares some danger for clumsy admins.

Maybe you cannot prevent clumsy ppl from shooting themselves in the foot sometimes. It's not too hard to write a command and an e-mail-address on one line. I just wanted to let you know, that one of our list-admins managed to pull that of.

Assignee
Assign to
4.0
Milestone
4.0
Assign milestone
Time tracking
None
Due date
None
Reference: schleuder/schleuder#364