Resolved -
We are pleased to inform you that the incident has been resolved. The issue was caused by a false classification of our Email domain in Microsoft's Global Email Infrastructure. The issue has now been fully mitigated by Microsoft. As a result, some customers may still experience emails being restored in their mailboxes. We appreciate your patience and understanding during this resolution process
Jul 23, 16:51 CEST
Update -
Microsoft has confirmed that they are actively working to resolve this issue. Customers may notice SoSafe emails from up to a week ago being restored to their mailboxes. We will continue to monitor the situation and provide updates as needed. The SoSafe team apologizes for any inconvenience this issue may have caused our customers.
Jul 22, 20:12 CEST
Update -
We are currently experiencing continued disruptions in email deliverability to some Microsoft Office 365 tenants due to the incorrect blacklisting of SoSafe's operational domains (sosafe-awareness.com). Our team is actively collaborating with Microsoft to resolve this issue on a global scale.
You can find more information here: https://support.sosafe.de/INFO/current-email-service-disruption-for-microsoft-ten
Jul 19, 16:53 CEST
Update -
We are continuing to monitor for any further issues.
Jul 18, 15:53 CEST
Update -
We are continuing to monitor for any further issues.
Jul 18, 09:01 CEST
Monitoring -
We can confirm that emails should now be sent successfully. We will continue to monitor the results.
Jul 17, 14:42 CEST
Identified -
The issue has been identified and a fix is being implemented.
Jul 17, 11:03 CEST
Update -
Our team of engineers is still working on the incident. The issue is currently affecting all of SoSafe E-Learning Platform related E-Mails, this includes but is not limited to:
- modules & demo emails
- reminder emails
- password reset emails
Jul 16, 17:00 CEST
Update -
We are continuing to investigate this issue.
Jul 16, 15:11 CEST
Update -
Our team continues to investigate this issue.
Jul 16, 15:11 CEST
Update -
We are continuing to investigate this issue.
Jul 16, 12:25 CEST
Investigating -
We are currently investigating this issue.
Jul 16, 10:03 CEST