mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2524] Enabling/Disabling SpamFilter #1269
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#1269
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 @BNWEIN on GitHub (Jun 6, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2524
Description
This currently fails in both the front end, and the API with error:
System.Management.Automation.RuntimeException: |Microsoft.Exchange.Data.Directory.InsufficientPermissionsException|Source server:LO3P123MB2985.GBRP123.PROD.OUTLOOK.COM doesn't have write permission to target DC:. Usually it indicates that target forest isn't an account partition of source forest. The user has insufficient access rights.
I would assume its missing an -anchor
Environment data
@github-actions[bot] commented on GitHub (Jun 6, 2024):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@BNWEIN commented on GitHub (Jun 6, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug
@BNWEIN commented on GitHub (Jun 6, 2024):
This one is a bit strange, because once in a while it does work, but if you manage to enable it and then try and disable it a few minutes later it fails.
@KelvinTegelaar commented on GitHub (Jun 6, 2024):
Fixed in dev by @kris6673