Hi Jaime, sorry to hear you're having trouble with this! I didn't find any other complaints on this so I did some testing of my own and I too am seeing result code 1000 on scanned messages. I don't believe thats working as expected so I'm going to do some additional testing and get a task escalated to our development team to take a look. Thanks for reporting this!

Thanks Kyle! 

We have reported this very issue via ticket to SM on Sep 18, 2024; we never were able to figure out a solution as the trouble-shooting requested on our end was too time-consuming. The error was persistent even after completely reinstalling SmarterMail.

We ended up not being to use Message Sniffer for the majority of the subscription period, and when the renewal came up recently, we opted not to renew that service. Accordingly, we cannot test this further.

Just wanted to share.

Drew

Thanks for the info Drew, we just renewed the yearly Message sniffer license, so I really hope this gets solved.  It just started failing when upgrading to SM latest version. 

Sorry to hear that Drew. We did have a Message Sniffer startup issue not too long ago that was resolved and this may have been affecting your environment the time. We're going to work on getting this issue above resolved and hopefully that'll be the end of those troubles!

I just finished testing Message Sniffer scanning against Windows, bare metal Linux, and docker-based Linux installations and all are functioning as I would expect at this point so we should have a public release out in the near future containing those fixes for you. Thanks for getting this reported!