[GH-ISSUE #4068] [Feature Request]: Exchange outbound anti-spam policy #1846

Closed
opened 2026-03-02 13:47:34 +03:00 by kerem · 3 comments
Owner

Originally created by @georgychacko007 on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4068

Originally assigned to: @Zacgoose on GitHub.

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

This feature will eliminate need of a custom policy to manage outboud spam

Benefits for MSPs

It can reduce manual work

Value or Importance

Hi,

Can we add an option in standard to enable the outbound anti-spam policy to limit the message sending.
This was already requested feature. Please see below url.
https://github.com/KelvinTegelaar/CIPP/issues/2942

PowerShell Commands (Optional)

Set-HostedOutboundSpamFilterPolicy -Identity Default -RecipientLimitExternalPerHour 750 -RecipientLimitInternalPerHour 750 -RecipientLimitPerDay 900 -ActionWhenThresholdReached BlockUser

Originally created by @georgychacko007 on GitHub (May 8, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4068 Originally assigned to: @Zacgoose on GitHub. ### 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 This feature will eliminate need of a custom policy to manage outboud spam ### Benefits for MSPs It can reduce manual work ### Value or Importance Hi, Can we add an option in standard to enable the outbound anti-spam policy to limit the message sending. This was already requested feature. Please see below url. https://github.com/KelvinTegelaar/CIPP/issues/2942 ### PowerShell Commands (Optional) Set-HostedOutboundSpamFilterPolicy -Identity Default -RecipientLimitExternalPerHour 750 -RecipientLimitInternalPerHour 750 -RecipientLimitPerDay 900 -ActionWhenThresholdReached BlockUser
Author
Owner

@Zacgoose commented on GitHub (May 8, 2025):

I would like to work on this please!

<!-- gh-comment-id:2861682854 --> @Zacgoose commented on GitHub (May 8, 2025): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!

<!-- gh-comment-id:2861683056 --> @github-actions[bot] commented on GitHub (May 8, 2025): Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
Author
Owner

@github-actions[bot] commented on GitHub (May 13, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

<!-- gh-comment-id:2876016666 --> @github-actions[bot] commented on GitHub (May 13, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**
Sign in to join this conversation.
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#1846
No description provided.