mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #3952] [Bug]: Quarantine release and allow sender fails to allow sender. #1779
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1779
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nkolcipp on GitHub (Apr 11, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3952
Required confirmations before submitting
Issue Description
When releasing an email from Quarantine and allowing the sender (Quarantine>Select Message>Release & Allow Sender). The email is released from quarantine, but I get the error message below and the sender is not added to the allow list.
Failed. |System.Management.Automation.CommandNotFoundException|The term 'Get-HostedContentFilterPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Environment Type
Sponsored (paying) user
Front End Version
v7.4.2
Back End Version
v7.4.2
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Apr 11, 2025):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@OfficialEsco commented on GitHub (Apr 11, 2025):
@KelvinTegelaar https://github.com/KelvinTegelaar/CIPP/issues/3743 would like to have a word with you again
@HappyEarthDay commented on GitHub (Apr 30, 2025):
We have also experienced this.
@KelvinTegelaar commented on GitHub (May 15, 2025):
So this issue is not on our side but MS; they are chaining commands together which sometimes fails. The commands do execute but just return a weird-ass error. Closed as a "cant fix"