mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4068] [Feature Request]: Exchange outbound anti-spam policy #1846
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#1846
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 @georgychacko007 on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4068
Originally assigned to: @Zacgoose on GitHub.
Please confirm:
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
@Zacgoose commented on GitHub (May 8, 2025):
I would like to work on this please!
@github-actions[bot] commented on GitHub (May 8, 2025):
Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!
@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