Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerts are not getting through to the configured email #2082

Closed
Lenwe666 opened this issue Feb 3, 2024 · 4 comments
Closed

Alerts are not getting through to the configured email #2082

Lenwe666 opened this issue Feb 3, 2024 · 4 comments
Labels
bug Something isn't working unconfirmed-by-user

Comments

@Lenwe666
Copy link

Lenwe666 commented Feb 3, 2024

Description

I've configured my email address in Application Settings > notifications and applied all severities. I've then setup a few rules for a specific tenant (ex: when an account is enabled/disabled) and manual disabled one in O365 admin portal to trigger the alert, but no email is received.

I've looked in my Inbox, Junk Email, Office365 quarantine and searched via the Message Trace, but no email has come through. Is some extra configuration needed for this? I looked in the documentation, but the page for "Alerting setup" is still empty.

Also, how are the email alerts send exactly? Is that using the Exchange server of our tenant or a general one for all CIPP users? Do we need to configure the SMTP settings anywhere or can they be changed to our own SMTP server (ex Office365 via Modern Authentication)?

Environment data

Non-sponsored instance
Front end version number: 5.0.1
Back end version number: 5.0.5
Tried Tenant Cache Clear: true
Tried Token Cache Clear: true
@Lenwe666 Lenwe666 added bug Something isn't working unconfirmed-by-user labels Feb 3, 2024
Copy link

github-actions bot commented Feb 3, 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!".

@Lenwe666
Copy link
Author

Lenwe666 commented Feb 3, 2024

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

@KelvinTegelaar
Copy link
Owner

Support issue, not a bug. If you need support you require sponsorship.

@shaun-cns
Copy link

@Lenwe666 did you ever figure it out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed-by-user
Projects
None yet
Development

No branches or pull requests

3 participants