Resolved -
This issue is now fully resolved - the contacts that were marked as undeliverable have been reset and the technical fixes are maintaining the performance expected.
Thanks for your understanding. If you have any questions relating to this issue please contact us in support.
The sheepCRM Team.
Feb 10, 17:25 GMT
Update -
Our monitoring is confirming the fixes are providing the results expected - we continue to monitor this but conclude the technical issue is now resolved.
Our logs show that over 99.9% of emails affected since 6 Feb have now been delivered successfully. Emails sent between 3 and 5 Feb to outlook, msn and hotmail addresses may not have delivered. As a result some email addresses have been incorrectly marked as "undeliverable". We are working to identify and revert this records to complete a full resolution for customers.
We will provide final update when fully resolved.
Feb 10, 10:23 GMT
Monitoring -
Further technical fixes have been applied. Microsoft have also supported with changes their side.
As of now emails for these domains are delivering without delays, but we are monitoring for 24hrs due so that peaks in volume are checked.
Should this continue to meet expectations we will move to customer resolution actions - further updates will be posted.
Thank you for your understanding throughout this issue to date.
Feb 9, 18:15 GMT
Identified -
Our team has identified the cause of the issue and have made some immediate changes but they are still working on a full fix and resolution actions.
A number of delayed emails are now successfully being delivered.
We appreciate your understanding while we continue our work to resolve this.
Feb 9, 15:01 GMT
Investigating -
We are currently investigating an issue that is causing email delivery delays or rejections to Microsoft email addresses (@outlook.com, @hotmail.com).
When an email fails to arrive, this results in the affected contact being auto-tagged with "undeliverable_email" and the contact is marked with "Automated (sheepCRM) emails are turned off" to avoid issue recurrence.
We appreciate your patience while we work to resolve this.
Feb 9, 11:45 GMT