Resolved -
Agileware have implemented a different email routing solution and email services are again operational. Some customers are managing their own DNS and we are reaching out to those few customers to advise necessary changes for this solution.
Oct 27, 16:52 AEDT
Update -
The temporary block is still active and affecting some customers. We are taking steps to change our email services to bypass this block and resume normal email delivery.
Oct 27, 12:20 AEDT
Update -
We have checked the status of the temporary block on email services and determined that not all customers are impacted. Customers have been notified if their email service continues to be impacted and notified if email services are back to normal.
Oct 26, 14:18 AEDT
Update -
We continue to wait for the anti-spam service to action the removal request which was submitted when the issue was initially identified. Should the issue not be resolved by Monday, we will be taking steps to implement an alternative email services for each customer.
Oct 26, 09:06 AEDT
Identified -
Agileware are aware of a current issue that is affecting email delivery due to a temporary block. You may experience problems with emails you send not being delivered to their recipients. A widely-used anti-spam filter has flagged multiple networks that our servers use, causing many email providers to block messages sent from your account. Agileware have already worked with our hosting provider to resolve the underlying cause. The hosting provider has been in direct contact with the anti-spam service and have requested the block be removed immediately.
To help resolve this situation as quickly as possible, we strongly advise you to postpone sending any email newsletters, marketing campaigns, or other bulk emails until we confirm this issue is fixed.
Sending large volumes of email while this block is active can make the problem worse and significantly delay the removal process.
We sincerely apologise for the inconvenience and disruption this is causing to your communications. We are working to have this resolved as fast as possible.
Oct 24, 09:53 AEDT