starred/CIPP

Fork 0

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

[GH-ISSUE #5098] [Feature Request]: Ability to View, add or remove Safe Sender domains in Outlook for one or all mailboxes #2430

New issue

Closed

opened 2026-03-02 13:52:15 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:52:15 +03:00

Owner

Originally created by @alexxdavid on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5098

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

Ability to see what users have set as safe sennders and domains in their mailbox.

Benefits for MSPs

This helps to deploy and monitor senders domains when needed for example when a phishing simulation is to be done

Value or Importance

Ability to remove manually or deploy automatically safe senders without relying on the Standard as the Standard affects all mailboxes

PowerShell Commands (Optional)

Add Safe Senders:

$users = Get-EXOMailbox -ResultSize unlimited
$senders = "example@example.com" #add safe senders here, in quotes and comma-separated
foreach($user in $users){
$out = 'Adding Trusted Senders to {0}' -f $user.UserPrincipalName
Write-Output $out
Set-MailboxJunkEmailConfiguration $user.UserPrincipalName -TrustedSendersAndDomains @{Add=$senders}
}
Write-Output "Finished!"

Verify Safe Senders:

$users = Get-EXOMailbox -ResultSize unlimited
foreach($user in $users){
$out = ‘Getting Trusted Senders from {0}' -f $user.UserPrincipalName
Write-Output $out
Get-MailboxJunkEmailConfiguration $user.UserPrincipalName
}
Write-Output "Finished!"

Remove Safe Senders:

$users = Get-EXOMailbox -ResultSize unlimited
$senders = "example@example.com" #add safe senders here,
in quotes and comma-separated
foreach($user in $users){
$out = 'Removing Trusted Senders from {0}' -f $user.UserPrincipalName
Write-Output $out
Set-MailboxJunkEmailConfiguration $user.UserPrincipalName -TrustedSendersAndDomains @{Remove=$senders}
}
Write-Output "Finished!"

Originally created by @alexxdavid on GitHub (Dec 16, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5098 ### 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 Ability to see what users have set as safe sennders and domains in their mailbox. ### Benefits for MSPs This helps to deploy and monitor senders domains when needed for example when a phishing simulation is to be done ### Value or Importance Ability to remove manually or deploy automatically safe senders without relying on the Standard as the Standard affects all mailboxes ### PowerShell Commands (Optional) **Add Safe Senders:** $users = Get-EXOMailbox -ResultSize unlimited $senders = "example@example.com" #add safe senders here, in quotes and comma-separated foreach($user in $users){ $out = 'Adding Trusted Senders to {0}' -f $user.UserPrincipalName Write-Output $out Set-MailboxJunkEmailConfiguration $user.UserPrincipalName -TrustedSendersAndDomains @{Add=$senders} } Write-Output "Finished!" **Verify Safe Senders:** $users = Get-EXOMailbox -ResultSize unlimited foreach($user in $users){ $out = ‘Getting Trusted Senders from {0}' -f $user.UserPrincipalName Write-Output $out Get-MailboxJunkEmailConfiguration $user.UserPrincipalName } Write-Output "Finished!" **Remove Safe Senders:** $users = Get-EXOMailbox -ResultSize unlimited $senders = "example@example.com" #add safe senders here, in quotes and comma-separated foreach($user in $users){ $out = 'Removing Trusted Senders from {0}' -f $user.UserPrincipalName Write-Output $out Set-MailboxJunkEmailConfiguration $user.UserPrincipalName -TrustedSendersAndDomains @{Remove=$senders} } Write-Output "Finished!"

kerem

2026-03-02 13:52:15 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:52:16 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 16, 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

@github-actions[bot] commented on GitHub (Dec 16, 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**

kerem commented

2026-03-02 13:52:16 +03:00

Author

Owner

@alexxdavid commented on GitHub (Dec 16, 2025):

@alexxdavid commented on GitHub (Dec 16, 2025): <img width="1068" height="392" alt="Image" src="https://github.com/user-attachments/assets/f9a9f168-a5c9-4724-ac65-825711473e17" />

kerem commented

2026-03-02 13:52:16 +03:00

Author

Owner

@kris6673 commented on GitHub (Dec 16, 2025):

https://github.com/KelvinTegelaar/CIPP/pull/5092 Is this good enough? Adding he ability to add safe senders should be redundant as you can already add stuff to the tenant allow list via CIPP already :)

@kris6673 commented on GitHub (Dec 16, 2025): https://github.com/KelvinTegelaar/CIPP/pull/5092 Is this good enough? Adding he ability to add safe senders should be redundant as you can already add stuff to the tenant allow list via CIPP already :)

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#2430

No description provided.

Rows
Columns