12-18-2017 05:19 AM - edited 03-08-2019 07:29 PM
Received critical as below. Is there any solution to resolve this issue.
The Critical message is:
MID 516702454 cannot be scanned by CASE. The message is either malformed or CASE is unable to process it at the moment.
Version: 9.7.1-066
Serial Number:
Timestamp: 17 Dec 2017 02:59:58 -0600
Solved! Go to Solution.
12-18-2017 06:15 AM
Hi,
This message is generally caused by a corrupted e-mail which has bad base64 encoding or corrupted mime parts that could not be scanned by CASE engine properly.
I see quite a few instances of these errors were reported over the weekend and we are working on a fix on our end.
TALOS has incorporated updates to the CASE URL Database in an attempt alleviate the issues we have been encountering with messages from *inthebox.com.
This was done around 2:30am Pacific Time.
Are you seeing any improvements? Have the number of alerts generated reduced?
Regards,
Libin Varghese
12-18-2017 06:15 AM
Hi,
This message is generally caused by a corrupted e-mail which has bad base64 encoding or corrupted mime parts that could not be scanned by CASE engine properly.
I see quite a few instances of these errors were reported over the weekend and we are working on a fix on our end.
TALOS has incorporated updates to the CASE URL Database in an attempt alleviate the issues we have been encountering with messages from *inthebox.com.
This was done around 2:30am Pacific Time.
Are you seeing any improvements? Have the number of alerts generated reduced?
Regards,
Libin Varghese
12-18-2017 08:08 AM
We've been having this issue as well since Thursday of last week. Will have to see if the update they made this morning resolves the problem.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: