Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
schleuder
schleuder
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 106
    • Issues 106
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • schleuder
  • schleuderschleuder
  • Issues
  • #48

Closed
Open
Opened Aug 14, 2015 by paz@paz
  • Report abuse
  • New issue
Report abuse New issue

If resending fails don't send message over list.

In case the resending failed (e.g. encrypted_only and no key), don't send the message to subscribers but reply to the sender to spare everyone a useless message.

If there are multiple resend-requests we should only abort if the first one fails. After sending out the message to the first resend-recipient it is "out there" and we should send the message also over the list.

Assignee
Assign to
Future
Milestone
Future
Assign milestone
Time tracking
None
Due date
None
2
Labels
Considering feature
Assign labels
  • View project labels
Reference: schleuder/schleuder#48