starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #4496] [Feature Request]: Allow editing of more options in anti-spam policies #2061

New issue

Closed

opened 2026-03-02 13:49:20 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 13:49:20 +03:00

Owner

Originally created by @CRoseProtek on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4496

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

I opened this issue already but it was closed, I do have a screenshot of our sponsorship payment but unsure the best way or providing this to Kelvin.
(original issue https://github.com/KelvinTegelaar/CIPP/issues/4420)

Original issue-
I searched the feature requests and I do not see it, please make me aware if I missed something 😊
(Closest one I found was https://github.com/KelvinTegelaar/CIPP/issues/3906)

The basic idea here is that CIPP already has the ability to deploy Policies via the standards & templates, but we do not get full control of the policy deployment.
For example the anti-spam policy deploys with the SPF hard fail setting enabled and is not adjustable from the standards template in CIPP.

If we could import a policy that we have in .json format and mass deploy it to clients that would be ideal.
This way we can stipulate the policy name we want, what settings we want enabled, what status to deploy in, etc without it needing to be defined as a standard by CIPP devs.

It would be great if we could also export policies that CIPP can see to .json so we can quickly iterate and mass-deploy.

Benefits for MSPs

This would reduce manual work the same way that standards do however with the added benefit of configuration and general wide-applicability.
Specifically for my MSP, we would use this to deploy policies that have the settings we need with our branded name rather than the "CIPP Anti-Spam" default names.

Value or Importance

This is borderline critical for my MSP, but we will be pursuing this using CIPPAPImodule.
The reason this would be nice to have is that CIPP wouldn't need to keep up with Microsoft in defining standards for it's users.
This .json approach would enable advanced users to have more customization and management over what is being deployed with what settings.

PowerShell Commands (Optional)

No response

Originally created by @CRoseProtek on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4496 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement I opened this issue already but it was closed, I do have a screenshot of our sponsorship payment but unsure the best way or providing this to Kelvin. (original issue https://github.com/KelvinTegelaar/CIPP/issues/4420) Original issue- I searched the feature requests and I do not see it, please make me aware if I missed something 😊 (Closest one I found was https://github.com/KelvinTegelaar/CIPP/issues/3906) The basic idea here is that CIPP already has the ability to deploy Policies via the standards & templates, but we do not get full control of the policy deployment. For example the anti-spam policy deploys with the SPF hard fail setting enabled and is not adjustable from the standards template in CIPP. If we could import a policy that we have in .json format and mass deploy it to clients that would be ideal. This way we can stipulate the policy name we want, what settings we want enabled, what status to deploy in, etc without it needing to be defined as a standard by CIPP devs. It would be great if we could also export policies that CIPP can see to .json so we can quickly iterate and mass-deploy. ### Benefits for MSPs This would reduce manual work the same way that standards do however with the added benefit of configuration and general wide-applicability. Specifically for my MSP, we would use this to deploy policies that have the settings we need with our branded name rather than the "CIPP Anti-Spam" default names. ### Value or Importance This is borderline critical for my MSP, but we will be pursuing this using [CIPPAPImodule](https://www.powershellgallery.com/packages/CIPPAPIModule/1.2.8). The reason this would be nice to have is that CIPP wouldn't need to keep up with Microsoft in defining standards for it's users. This .json approach would enable advanced users to have more customization and management over what is being deployed with what settings. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:49:20 +03:00

closed this issue
added the
enhancement

no-priority

no-activity

not-assigned
labels

kerem commented

2026-03-02 13:49:20 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Aug 4, 2025):

While we wont allow you to import your own, we can make those settings available as switches now. @JohnDuprey roadmap this please :)

@KelvinTegelaar commented on GitHub (Aug 4, 2025): While we wont allow you to import your own, we can make those settings available as switches now. @JohnDuprey roadmap this please :)

kerem commented

2026-03-02 13:49:20 +03:00

Author

Owner

@CRoseProtek commented on GitHub (Aug 4, 2025):

Thank you Kelvin!
Also, appreciated your time on today's cyber call :)

@CRoseProtek commented on GitHub (Aug 4, 2025): Thank you Kelvin! Also, appreciated your time on today's cyber call :)

kerem commented

2026-03-02 13:49:21 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 15, 2025):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Aug 15, 2025): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 13:49:21 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 21, 2025):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Aug 21, 2025): This issue was closed because it has been stalled for 14 days with no activity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2061

No description provided.

Rows
Columns