Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-orchestrator fusiondirectory-orchestrator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-orchestratorfusiondirectory-orchestrator
  • Issues
  • #5
Closed
Open
Issue created Dec 12, 2022 by dockx thibault@tdockxMaintainer

[Orchestrator] - Verification of the time execution between two SPAM protection timelapse.

Requirements

Verification of the time set between two batch of emails is respected properly.

Descriptive title for this enhancement

[Orchestrator] - Verification of the time of execution between two SPAM protection time-lapse.

Actual behavior

It might be that in some circumstances the time-lapse between two emails batches sent is not respected.

Expected behavior

Respect of the time set between sending multiples emails, respecting the spam protection.

Step by step description of new behavior

Set a minimum of 1 emails between batch, send 1 fake email and see if the second one is being send below the delay set between batch.

Benefits

Proper spam protection management.

Possible Drawbacks

None.

Applicable Issues

Assignee
Assign to
Time tracking