Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • castellum castellum
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Castellum
  • castellumcastellum
  • Issues
  • #151

Closed
Open
Created Jan 12, 2022 by Bengfort@bengfortOwner

Properly handle mail exceptions

Exceptions can still happen when sending mail, e.g. when we reach a limit and get blocked by the mail server.

This is an issue if we send a list of emails and then update the database in a final step. If send_mail() crashes somewhere in the list, the first few mails have already been send, but the database is never updated to reflect that.

This was fixed for mail recruitment in !2217 (merged). There are many other cases though that need a similar fix.

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